Arch Linux User Repository

You can fix the GPG key issue by using:

curl -sS https://download.spotify.com/debian/pubkey_5E3C45D7B312C643.gpg | gpg --import -

out of date now.

For what it's worth I can confirm that as @HurricanePootis says, playback of local files still works after removing ffmpeg-compat-57. Always nice to be able to remove such an outdated package.

Hey, I just did some testing with spotify, and it seems like at least spotify version 1.1.18.716, spotify doesn't require ffmpeg-compat-57 for playing local files.

Instead, after doing some testing, spotify now relies on the ffmpeg4.4 package for the playback of local files.

Therefore, ffmpeg-compat-57 should be replace with ffmpeg4.4 for local playblack of files

diff --git a/PKGBUILD b/PKGBUILD
index 58ad0db..c2dab8a 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -4,16 +4,16 @@
 # Contributor: Eothred <yngve.levinsen@gmail.com>

 pkgname=spotify
-pkgver=1.1.80.699
+pkgver=1.1.84.716
 epoch=1
-_commit=gc3dac750
+_commit=gc5f8b819
 pkgrel=1
 pkgdesc='A proprietary music streaming service'
 arch=('x86_64')
 license=('custom')
 url='https://www.spotify.com'
 depends=('alsa-lib>=1.0.14' 'gtk3' 'libxss' 'desktop-file-utils' 'openssl' 'nss' 'at-spi2-atk' 'libcurl-gnutls' 'libsm')
-optdepends=('ffmpeg-compat-57: Adds support for playback of local files'
+optdepends=('ffmpeg4.4: Adds support for playback of local files'
             'zenity: Adds support for importing local files'
             'libnotify: Desktop notifications')
 options=('!strip')
@@ -33,7 +33,7 @@ source=('spotify.protocol'
         "${pkgname}-${pkgver}-${pkgrel}-x86_64-Packages::http://repository.spotify.com/dists/testing/non-free/binary-amd64/Packages")
 sha512sums=('999abe46766a4101e27477f5c9f69394a4bb5c097e2e048ec2c6cb93dfa1743eb436bde3768af6ba1b90eaac78ea8589d82e621f9cbe7d9ab3f41acee6e8ca20'
             '2e16f7c7b09e9ecefaa11ab38eb7a792c62ae6f33d95ab1ff46d68995316324d8c5287b0d9ce142d1cf15158e61f594e930260abb8155467af8bc25779960615'
-            'ea3ad8b5e320f42945fe0fdc764fb50fa145805f49ff4762f81e76c38e84a4a4da3039848882332315ab694aa0c9cfb808a6ad0b4ac7ec625ef5fe1e8a646734'
+            '3cc25f28ae791ac26607117a5df668f803ed8e58f0ace085010a6242fdde97766bdc1c752560850795c9b4324f3e019937fe9af2788a1946ebb70ee781f50d99'
             'SKIP'
             'SKIP'
             'SKIP')

Сhecksums to current date

sha512sums=('999abe46766a4101e27477f5c9f69394a4bb5c097e2e048ec2c6cb93dfa1743eb436bde3768af6ba1b90eaac78ea8589d82e621f9cbe7d9ab3f41acee6e8ca20'
            '2e16f7c7b09e9ecefaa11ab38eb7a792c62ae6f33d95ab1ff46d68995316324d8c5287b0d9ce142d1cf15158e61f594e930260abb8155467af8bc25779960615'
            '3cc25f28ae791ac26607117a5df668f803ed8e58f0ace085010a6242fdde97766bdc1c752560850795c9b4324f3e019937fe9af2788a1946ebb70ee781f50d99'
            'SKIP'
            'SKIP'
            'SKIP')

@aidenscott2016

List of changes made to ./PKGBUILD to get it working:

Change up the package version and commit hash -

pkgver=1.1.84.716
_commit=gc5f8b819

Skip the third checksum -

sha512sums=('999abe46766a4101e27477f5c9f69394a4bb5c097e2e048ec2c6cb93dfa1743eb436bde3768af6ba1b90eaac78ea8589d82e621f9cbe7d9ab3f41acee6e8ca20'
            '2e16f7c7b09e9ecefaa11ab38eb7a792c62ae6f33d95ab1ff46d68995316324d8c5287b0d9ce142d1cf15158e61f594e930260abb8155467af8bc25779960615'
            'SKIP'
            'SKIP'
            'SKIP'
            'SKIP')

NOTE: There's an argument to figure out a way to get the proper package checksum here, but in my case it's a bit of a chicken/egg problem to ensure the checksum is actually meaningful so I gave up and just skipped it.

-> Flagged Out Of Date AUR Packages: spotify

I have updated the build locally, but unfortunately I don't see a way to raise a PR on aur

source for deb in build is currently dead. new link is http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.84.716.gc5f8b819_amd64.deb

I have created an AUR package for version 1.1.42 so XFCE users like me can get the track printed in the titlebar again.

https://aur.archlinux.org/packages/spotify-1.1.42-deb

@MarsSeed, thank you for the info. I'll stay on 1.1.72 for now then, since it looks like this update brings no benefits and or fixes, and I have some custom modifications to Spotify that are a bit of a pain in the ass to apply.

So.. if it isn't out of date, just remove the out-of-date flag. Just my two cent

@Sanras I'm using the current version (1.1.80.699), and yes, its titlebar still shows the Xorg icon and only the word 'Spotify'.

But I don't notice this as a problem because I use a dark titlebar window decoration on KDE Plasma.

So it blends well with the dark interface of Spotify.

@Archanfel80HUN I understand that you want to help.

But please be considerate, don't propose a fix for a nonexistent problem.

Especially not if your proposal introduces problems on its own.

Making this package explicitly depend on libcurl3-gnutls would force users to uninstall the current libcurl-gnutls that provides v4, and would break any dependents on their system that require that version.

@MarsSeed I post this coz i see the flag status too, this "fix" it if dinnymate complained about this. But the point is the package is not out of date. I try to help this dude.

@HurricanePootis who flagged the package report with the reason what i post below. Dont know why flagged either. Its not out of date. Flag should be removed, its confusing.

Those of you on the latest 1.1.80 release of Spotify, does the titlebar text work again in this version? Or does it still have the X11 icon and only show Spotify?

Bruh who flagged this package, that line has always showed in spotify for me, and never affected spotify from working the way it's intended.

@Archanfel80HUN & @dinnymate (who flagged this package because of an info log),

Why are you concerned with that info log line?

What's important is that the package libcurl-gnutls provides both v3 and v4 of the .so library:

• usr/lib/libcurl-gnutls.so.3
• usr/lib/libcurl-gnutls.so.4

Spotify still works. No change is needed.

Problem: /opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify) /proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)

Solution: replace libcurl-gnutls with libcurl3-gnutls (libcurl with libcurl3 versioned symbols)

Its not out of date, why flagged? Latest version is still 1.80.699-1.

@NicoHood Regarding xorg/xorg-xwayland - you could depend on xorg-server-common? I assume that is the key commonality, a dependency of both xorg-xwayland (provides xorg-server-xwayland) & xorg-server (constituent of the xorg group).

Edit: Actually, sorry, that's probably not actually any good if you don't already have one of them installed, and would just be confusing. You'd want to install something that depended on xorg-server-common, not it itself. Ideally xorg-xwayland would provides xorg-server I suppose, then the dependency would be xorg-server, and installing would give the option of providers. But it doesn't currently, and I don't think it's supposed to unless it actually literally provides a binary of that name. Afaik there isn't an alternative for 'provides the functionality of'.

Spotify has been garbage since the new interface. I went back to the old version and write protected it as read-only so it wouldn't auto-update. We have lost so much functionality in the new player, even with spicetify, it's only a shadow of what it once was in terms of functionality and usefulness.

You can find old versions in deb format here: http://mirror.cs.uchicago.edu/spotify/pool/non-free/s/spotify-client/

Make sure to uninstall any version of Spotify you have first.

I recommend installing spotify-client_1.1.42.622.gbd112320-37_amd64.deb

To do this in arch, you could try debtap, downgrade software, or something to that effect. I just extracted the files from the deb and put them into the respective directories. It could also be done by modify the pkgbuild but that is a bit complicated. Make sure to delete the spotify directories in .config and .cache in your user home before launching the functional client. Also make sure you have installed the prerequisites for this version:

depends=('alsa-lib>=1.0.14' 'gtk2' 'libsystemd' 'libxss' 'desktop-file-utils' 'openssl' 'nss' 'at-spi2-atk') depends_x86_64=('libcurl-gnutls') depends_i686=('libcurl-compat') optdepends=('ffmpeg-compat-57: Adds support for playback of local files' 'zenity: Adds support for importing local files' 'libnotify: Desktop notifications')

One workaround is to run updpkgsums prior to running makepkg ...

For those encountering an error like

spotify-1.1.72.439-3-x86_64-Packages: OK
spotify-1.1.72.439-x86_64.deb: FAILED
sha512sum: WARNING: 1 computed checksum did NOT match

this is because the PKGBUILD uses 1.1.72 but the online packages-file from spotify provides hashes for 1.1.80 (probably since 10pm last night as the online page states). For me it worked to switch in the URLs from "testing" to "stable" in the PKGBUILD file. I know the release packages are not really up-to-date but a) I don't like the 1.1.80 client and b) this enables me to install spotify using this AUR package.

On the long term, this PKGBUILD file should of course be updated to use the latest version with its hashes.

spotify has updated there .deb release as you can see here - https://repository-origin.spotify.com/pool/non-free/s/spotify-client/ so please update this package

@BachoSeven There are several packages in AUR which are based on snap sources, one example is authy. I don't see your point of how (not) convenient a snap package is. On snapcraft is an official Spotify stable package release 1.1.77.643.g3c4c6fc6. This means this package here is either outdated or falsely named. It really looks like spotify stopped making deb releases last november if you compare their deb repo with the snap releases.

@Romario74 That is not the case; while on Snap they packaged v77, if you look here you will find that the Spotify devs have not been updating the .deb releases. Re-packaging Snaps is less convenient than using a .deb tarball, and is being done through scripts by this Github project, which is in turn repackaged by @Edu4rdSHL.

This package should be renamed to spotify-deb because it falsely claims to be the latest stable spotiy.

I have created the spotify-snap package for those who want to use an updated version, https://aur.archlinux.org/packages/spotify-snap

No, it isn't. It provides the latest official deb package. Maybe the PKGBUILD for spotify-(edge-)snap can be restored and updated? That's what I use at the moment.

Because the package is out of date.

Why has the package been flagged out of date?

Why has the package been flagged out of date?

Updated to the github source + a few other changes

# Maintainer: Ashley Whetter <(firstname) @ awhetter.co.uk>
# Co-Maintainer: NicoHood <archlinux {cat} nicohood {dog} de>
# PGP ID: 97312D5EB9D7AE7D0BD4307351DAE9B7C1AE9161
# Contributor: Eothred <yngve.levinsen@gmail.com>

pkgname=spotify
pkgver=1.1.77.643
_commit=g3c4c6fc6
epoch=1
pkgrel=0
pkgdesc='A proprietary music streaming service'
arch=('x86_64')
license=('custom')
url='https://www.spotify.com'
depends=('alsa-lib>=1.0.14' 'gtk3' 'libxss' 'desktop-file-utils' 'openssl' 'nss' 'at-spi2-atk' 'libcurl-gnutls' 'libsm')
optdepends=('ffmpeg-compat-57: Adds support for playback of local files'
            'zenity: Adds support for importing local files'
            'libnotify: Desktop notifications')
options=('!strip')

# NOTE: We switched from stable to testing on 18th march, as the spotify
# stable repository is always outdated. Testing seems to be in sync with snap:
# https://snapcraft.io/spotify
# http://repository.spotify.com/dists/testing/Release
# http://repository.spotify.com/dists/testing/non-free/binary-amd64/Packages
# http://repository.spotify.com/dists/testing/Release.gpg
source=('spotify.protocol'
        'LICENSE'
        "${pkgname}-${pkgver}-x86_64.deb::https://github.com/ThePoorPilot/Unofficial-Spotify/releases/download/${pkgver}.${_commit}/spotify-unofficial_${pkgver}.${_commit}_amd64.deb"
)
sha512sums=('999abe46766a4101e27477f5c9f69394a4bb5c097e2e048ec2c6cb93dfa1743eb436bde3768af6ba1b90eaac78ea8589d82e621f9cbe7d9ab3f41acee6e8ca20'
            '2e16f7c7b09e9ecefaa11ab38eb7a792c62ae6f33d95ab1ff46d68995316324d8c5287b0d9ce142d1cf15158e61f594e930260abb8155467af8bc25779960615'
            'cd83989a10c5c3a95523112c1f55051738476415e7440477075a876eb032f1c2d1ba676c013f0ec674d60c245bdd3ff65425db8a52e655c615ce5b216398ffa1'
)

package() {
    cd "${srcdir}"

    tar -xf data.tar.xz -C "${pkgdir}"

    rm -rf "${pkgdir}"/usr/share/doc "${pkgdir}"/usr/share/spotify/apt-keys "${pkgdir}"/usr/share/spotify/icons/spotify_icon.ico

    # Enable spotify to open URLs from the webapp
    sed -i 's/^Exec=.*/Exec=spotify --uri=%U/' "${pkgdir}"/usr/share/spotify/spotify.desktop

    # Fix icon
    sed -i 's|^Icon=/usr/share/spotify/icons/spotify-linux-128.png|Icon=spotify|' "${pkgdir}"/usr/share/spotify/spotify.desktop

    mkdir -p "${pkgdir}"/usr/share/applications
    ln -sf /opt/spotify/spotify.desktop "${pkgdir}"/usr/share/applications/spotify.desktop

    for size in 22 24 32 48 64 128 256 512; do
        mkdir -p "${pkgdir}/usr/share/icons/hicolor/${size}x${size}/apps"
        ln -sf "/opt/spotify/icons/spotify-linux-$size.png" "${pkgdir}/usr/share/icons/hicolor/${size}x${size}/apps/spotify.png"
    done

    # Move spotify binary to its proper location
    mkdir -p "${pkgdir}"/opt/spotify
    mv "${pkgdir}/usr/share/spotify" "${pkgdir}/opt/"

    # Symlink spotify binary which is located in /opt
    ln -sf /opt/spotify/spotify "${pkgdir}/usr/bin/spotify"

    # Copy protocol file for KDE
    install -Dm644 "${srcdir}/spotify.protocol" "${pkgdir}/usr/share/kservices5/spotify.protocol"

    # Install license
    # https://www.spotify.com/legal/end-user-agreement
    install -Dm 644 LICENSE "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"

    # Fix permissions
    chmod -R go-w "${pkgdir}"
    chown -R root:root "${pkgdir}"
}

Seems like spotify didn't put it's latest client in their little online repository server. Thankfully, there is someone on Github who gets the latest .deb files from snap and uploads it as a github release here

I had the same issue as @miktwon, a clean build fixed it. Thanks for providing this!

I get these errors. Any ideas on how to fix / work around them?

error: could not extract /opt/spotify/libcef.so (Truncated zstd input)
error: problem occurred while upgrading spotify
error: could not commit transaction
error: failed to commit transaction (transaction aborted)
Errors occurred, no packages were upgraded.

EDIT: It was due to using paru (1.9.2-1). It works fine with yay (11.1.0-1)

I can confirm I also see this "Server X" icon for Spotify on the window switcher.

https://imgur.com/a/awntGcj

Plasma KDE: 5.23.5
X11 server: 21.1.3-1

Hey I have this problem on instalation

==> Starting prepare()...
grep: spotify-1.1.72.439-Release: No such file or directory
sha256sum: spotify-1.1.72.439-x86_64-Packages.sha256: no properly formatted checksum lines found

yay 11.1.0-1

could you please help

@marktos @NicoHood

Does anyone have a better idea?

It may be related to a previously reported bug related with notify-send.

I don't think libcurl is the issue here. Nor does Daniel need to had this issue to the wall of problems involving libcurl but don't have actually anything to do with libcurl.

@markstos that is a good hint. But I don't think there is a way to depend on A or B. Maybe I could add it as optional dependency? Does anyone have a better idea?

The package failed to start on Wayland until I installed xorg-xwayland. It seems like the package should depend on having one of xorg or xorg-xwayland installed.

Had to clean yay cache before upgrading.

After a fresh install of Arch Linux, I get the following error when attempting to launch. It's complaining about "/usr/lib/libcurl-gnutls.so.4", which is installed on the system.

spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
fish: Job 1, 'spotify' terminated by signal SIGSEGV (Address boundary error)

I confirm. I also have this "Server X" icon on Spotify when switching windows on alt+tab. I just never noticed it before.

@Sanras The workaround provided only works with Spotify Premium as the fullscreen button is a premium feature. Is there a way to fix this without Spotify Premium?

@norysq This is not an issue with you, it's an issue with this package. Seems to be happening to everyone, read through the older comments on this package.

I have the X-Server logo in the top left corner when using the GUI or the Alt-Tab menu on Garuda Linux (which is Arch-based). Version is latest. Any idea why this is happening? The Latte Dock displays the right icon.

About me:

OS: Garuda Linux KDE dr460nized

KDE Plasma: 5.23.4

Kernel: 5.15.7 linux-zen (64-bit)

Hope someone knows how to fix it? I think this is a me issue - not the package itself.

Thanks @haagch, your advice with deleting and importing new key worked! Update installed. Thanks again!

The relevant cache depends on your aur helper client. I use yay and paru and both have their own cache folder. Yay is ~/.cache/yay/spotify and paru is ~/.cache/paru/clone/spotify. Always helpful to read the docs from your helper.

Also, what cache was deleted? Pacman, in user space, build files or elsewhere?

I had the same problem and was able to fix the issue by

rm -rf /var/tmp/pamac-build-$USER/spotify

Need to delete the old key first

gpg --delete-key 8FD3D9A8D3800305A9FFF259D1742AD60D811D58

curl -sS https://download.spotify.com/debian/pubkey_5E3C45D7B312C643.gpg | gpg --import -

Found here: https://bbs.archlinux.org/viewtopic.php?pid=2007155#p2007155

I also have issue with the latest update and can't build it because of the unknown public key. As to the latest comment, it doesn't help, because I can't rebuild it, since the builds fail. Also, what cache was deleted? Pacman, in user space, build files or elsewhere?

I just rebuilt the whole package (deleted the cache before) and everything ran smooth

I've imported the GPG key but am still getting this error

==> Verifying source file signatures with gpg...
    spotify-1.1.72.439-3-Release ... FAILED
==> ERROR: One or more PGP signatures could not be verified!

@vimpostor crazy piece of a Exec line you got there! Must have been a lot of fun to create that with sed. Would be amazing if you could patch the existing sed line in the PKGBUILD with that addition? :)

Just kidding.. in my opinion there is no way to insert that one into the existing sed script in the PKGBUILD file, so shipping a own spotify.desktop file with this aur package and ignoring the original file from the spotify package sounds like the best way for me.

As a gnome user I can't recomment to insert the file in ~/.local/share/applications/spotify.desktop, when there is still the one in /usr/share/applications/spotify.desktop. Gnome displays both and there is no easy way to select the right one. I patched the /usr/share/applications/spotify.desktop with your Exec line and it works perfectly fine.

So my complete /usr/share/applications/spotify.desktop looks like that:

[Desktop Entry]
Type=Application
Name=Spotify
GenericName=Music Player
Icon=spotify-client
TryExec=spotify
Exec=env U=%u sh -c "pidof spotify && dbus-send --type=method_call --dest=org.mpris.MediaPlayer2.spotify /org/mpris/MediaPlayer2 org.mpris.MediaPlayer2.Player.OpenUri string:\\$(echo \\$U| sed 's/\\(https:\\/\\/open.spotify.com\\/\\|spotify:\\/\\/\\)\\(.*\\)\\/\\([[:alnum:]]*\\).*/spotify:\\2:\\3/'| sed 's/^\\(spotify:[a-z]*:[[:alnum:]]*\\)?.*/\\1/') || spotify --uri=\\$U"
Terminal=false
MimeType=x-scheme-handler/spotify;
Categories=Audio;Music;Player;AudioVideo;
StartupWMClass=spotify

@sam9032 Thanks for the desktop file fixing xdg-open with Spotify. Unfortunately it would open the track in a new Spotify instance, even if one was already running.

Below is a fixed Exec line, that opens links in the already running Spotify instance if existing (don't worry, it is only so long because it needs to handle three different Spotify URI formats):

Exec=env U=%u sh -c "pidof spotify && dbus-send --type=method_call --dest=org.mpris.MediaPlayer2.spotify /org/mpris/MediaPlayer2 org.mpris.MediaPlayer2.Player.OpenUri string:\\$(echo \\$U| sed 's/\\(https:\\/\\/open.spotify.com\\/\\|spotify:\\/\\/\\)\\(.*\\)\\/\\([[:alnum:]]*\\).*/spotify:\\2:\\3/'| sed 's/^\\(spotify:[a-z]*:[[:alnum:]]*\\)?.*/\\1/') || spotify --uri=\\$U"

To use this, run cp /usr/share/applications/spotify.desktop ~/.local/share/applications/spotify.desktop, exchange the matching line in the desktop file and run update-desktop-database ~/.local/share/applications.

Ultimately, this desktop file should be shipped in its entirety with this spotify package in my opinion though.

EDIT: just saw segment0's diff, which is cleaner.

@nicohood would you be able to path the PKGBUILD file? Happy to do so myself, but here's a functional Git patch for the time being.

diff --git a/PKGBUILD b/PKGBUILD
index de119fc..1800367 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -46,12 +46,16 @@ validpgpkeys=('F9A211976ED662F00E59361E5E3C45D7B312C643') # Spotify Public Repos
 # 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45

 prepare() {
+    # Identify release & package files
+    # Be tolerant of non-semver naming conventions
+    package_file=$(find . -mindepth 1 -maxdepth 1 -name "${pkgname}-${pkgversion}*-x86_64-Packages")
+    release_file=$(find . -mindepth 1 -maxdepth 1 -name "${pkgname}-${pkgversion}*-Release")
     # Validate hashes from the PGP signed "Release" file
-    echo "$(grep non-free/binary-amd64/Packages ${pkgname}-${pkgver}-Release | tail -n 2 | head -n 1 | awk '{print $1}') ${pkgname}-${pkgver}-x86_64-Packages" \
+    echo "$(grep non-free/binary-amd64/Packages "${release_file}" | tail -n 2 | head -n 1 | awk '{print $1}') ${package_file}" \
         > "${pkgname}-${pkgver}-x86_64-Packages.sha256"
     sha256sum -c "${pkgname}-${pkgver}-x86_64-Packages.sha256"

-    echo "$(grep SHA512 ${pkgname}-${pkgver}-x86_64-Packages | head -n 1 | awk '{print $2}') ${pkgname}-${pkgver}-x86_64.deb" \
+    echo "$(grep SHA512 "${package_file}" | head -n 1 | awk '{print $2}') ${pkgname}-${pkgver}-x86_64.deb" \
         > "${pkgname}-${pkgver}-x86_64.deb.sha512"
     sha512sum -c "${pkgname}-${pkgver}-x86_64.deb.sha512"
 }

The TL;DR is that is uses find to be more tolerant of the filenames when validating the checksums.

The error no properly formatted checksum lines found seems to be caused by using incorrect file names in prepare(). Specifically some of the files searched by grep is missing pkgrel in the names, resulting in no hashes found in the outputs.

The following changes should use the correct files.

diff --git a/PKGBUILD b/PKGBUILD
index de119fc..c46079a 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -47,11 +47,11 @@ validpgpkeys=('F9A211976ED662F00E59361E5E3C45D7B312C643') # Spotify Public Repos

 prepare() {
     # Validate hashes from the PGP signed "Release" file
-    echo "$(grep non-free/binary-amd64/Packages ${pkgname}-${pkgver}-Release | tail -n 2 | head -n 1 | awk '{print $1}') ${pkgname}-${pkgver}-x86_64-Packages" \
-        > "${pkgname}-${pkgver}-x86_64-Packages.sha256"
-    sha256sum -c "${pkgname}-${pkgver}-x86_64-Packages.sha256"
+    echo "$(grep non-free/binary-amd64/Packages ${pkgname}-${pkgver}-${pkgrel}-Release | tail -n 2 | head -n 1 | awk '{print $1}') ${pkgname}-${pkgver}-${pkgrel}-x86_64-Packages" \
+        > "${pkgname}-${pkgver}-${pkgrel}-x86_64-Packages.sha256"
+    sha256sum -c "${pkgname}-${pkgver}-${pkgrel}-x86_64-Packages.sha256"

-    echo "$(grep SHA512 ${pkgname}-${pkgver}-x86_64-Packages | head -n 1 | awk '{print $2}') ${pkgname}-${pkgver}-x86_64.deb" \
+    echo "$(grep SHA512 ${pkgname}-${pkgver}-${pkgrel}-x86_64-Packages | head -n 1 | awk '{print $2}') ${pkgname}-${pkgver}-x86_64.deb" \
         > "${pkgname}-${pkgver}-x86_64.deb.sha512"
     sha512sum -c "${pkgname}-${pkgver}-x86_64.deb.sha512"
 }

I can confirm that the latest PKGBUILD doesn't work until adding cd .. at the beginning of prepare().

You can fix the build error where it can't find the Packages.sha256 file by adding

cd ..

to the top of prepare() in the PKGBUILD. It seems to be searching builddir/src while the files it wants are in builddir

The cache removing workaround for yay didn't work, still the same error. Also noticed a different one beforehand:

grep: spotify-1.1.72.439-Release: No such file or directory
sha256sum: spotify-1.1.72.439-x86_64-Packages.sha256: no properly formatted checksum lines found

~/.cache/yay/spotify/src/spotify-1.1.72.439-x86_64-Packages.sha256

only has:

 spotify-1.1.72.439-x86_64-Packages

@NicoHood I tried both, it doesn't seem to matter. I would just keep it consistent with what is in the spotify.protocol file, but changing the spotify.protocol exec line to --uri instead of -uri.

yay -Syu gives

grep: spotify-1.1.72.439-Release: No such file or directory sha256sum: spotify-1.1.72.439-x86_64-Packages.sha256: no properly formatted checksum lines found

Tried: rm -rf ~/.cache/yay/spotify

Result: grep: spotify-1.1.72.439-Release: No such file or directory sha256sum: spotify-1.1.72.439-x86_64-Packages.sha256: no properly formatted checksum lines found ==> ERROR: A failure occurred in prepare(). Aborting... -> error making: spotify

@sam9032 Thanks for the fix! Small or capital u/U? In your diff you wrote u, in the comment U

Thats true. But he wrote, they know about the issues and they are all tracked internally in their bug tracker. But feel free, to open a new thread there. Maybe we get a few likes on that one, so it is more relevant to the spotify developers..

And in this thread, a spotify guy answers 2017 with the excact problems, which are still present..

Well, I don't think anything is gonna happen to this particular thread, because author chose some comment as a solution. So as far as Spotify support concerned, this thread basically doesn't exist.

@Hi-Angel, yes that would be the best solution, but i am not really confident, that they are fixing anything regarding the Linux client, if you read through the spotify forum. Especially this kind of issue was a few times there: https://community.spotify.com/t5/forums/searchpage/tab/message?filter=location&q=open%20link&location=forum-board:desktop_linux&collapse_discussion=true

And in this thread, a spotify guy answers 2017 with the excact problems, which are still present..

@sam9032 thank you for providing a nice workaround! What that said, could you please send a report to Spotify on this as well, so they'd fix it upstream?

This topic seems to tell how to create a report to Spotify.

Hey there, the standard Spotify package has a problem. If you open Spotify links with a browser and then want to open them with Spotify Desktop, it only opens Spotify but not the link. We could solve this problem by changing the spotify.desktop files. We need to replace Exec=spotify %U with Exec=spotify --uri=%U, the same as in the spotify.protocol file. After that, xdg-open, firefox etc. open the link correctly, if spotify hasn't started before.

We could change the PKGBUILD like that:

diff --git a/PKGBUILD b/PKGBUILD
index 16b0be5..50e738f 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -60,7 +60,7 @@ package() {
     cd "${srcdir}"

     tar -xzf data.tar.gz -C "${pkgdir}"
-
+    sed -i 's/^Exec=.*/Exec=spotify --uri=%u/' "${pkgdir}"/usr/share/spotify/spotify.desktop
     install -Dm644 "${pkgdir}"/usr/share/spotify/spotify.desktop "${pkgdir}"/usr/share/applications/spotify.desktop
     install -Dm644 "${pkgdir}"/usr/share/spotify/icons/spotify-linux-512.png "${pkgdir}"/usr/share/pixmaps/spotify-client.png

Note: simply adding the new key does not work, as the signature file has changed without changing the filename. You need to delete your old sources before building again.

@NicoHood you might want to change the filenames of spotify-1.1.72.439-Release and spotify-1.1.72.439-Release.sig so people will download the correct versions.

I just used yaourt to install it and it worked

I got it to work by deleting the old key as well as deleting the .cache/yay/spotify folder. Then ran the installation as usual. Thanks for the solution to knaick and pkr.

I had the gpg problem previously mentioned and I managed to update deleting the old key, downloading the new one (curl -sS https://download.spotify.com/debian/pubkey_5E3C45D7B312C643.gpg | gpg --import -) removing the installation folder, cloning the folder again and reinstalling. I feel I should not need to remove and replace the folder, does anyone have any suggestion about that? I am sure I need to refresh something, but I could not figure out what. (I am not using any AUR helper)

Thanks, deleting ~/.cache/yay/spotify helped me too

@pkr I didn't need to do that. I am also using yay.

Seems Paru didn't had any PGP issues. Always good to check why a new key was needed anyway. :)

For those still having trouble building the package after updating the gpg key, if you are using an AUR helper like paru, delete your cache (for paru it's .cache/paru/clone/spotify) and try again.

I needed to clear .cache/yay/spotify folder (yay user). At least that helped on my machine. Just removing the key didn't help. Probably it is more a problem with the .cache folder than an outdated pgp key as long you have the newest one in your keyring.

For the ones needing it: gpg --delete-key 8FD3D9A8D3800305A9FFF259D1742AD60D811D58- The old key expired. You need to remove it from GPG as it is no longer used.

@NicoHood: The key 8FD3D9A8D3800305A9FFF259D1742AD60D811D58 expired 3 days ago:

pub rsa4096 2020-09-08 [SC] [verfallen: 2021-12-02] 8FD3D9A8D3800305A9FFF259D1742AD60D811D58 uid [ verfallen ] Spotify Public Repository Signing Key tux@spotify.com

Guys, please update your gpg key. See the pinned comment! Stop flagging the package out of date!

The import of the key via curl does not work.

==> Validating source files with sha512sums... spotify.protocol ... Passed LICENSE ... Passed spotify-1.1.72.439-x86_64.deb ... Passed spotify-1.1.72.439-Release ... Skipped spotify-1.1.72.439-Release.sig ... Skipped spotify-1.1.72.439-x86_64-Packages ... Skipped ==> Verifying source file signatures with gpg... spotify-1.1.72.439-Release ... FAILED (invalid public key 8FD3D9A8D3800305A9FFF259D1742AD60D811D58) ==> ERROR: One or more PGP signatures could not be verified! -> error making: spotify

I'm also getting the error @Scotty_Trees is reporting. Interestingly, if I clone the package repository and manually makepkg, I have no such issue.

Tried updating Spotify AUR package today, got the following issue:

==> Verifying source file signatures with gpg...
    spotify-1.1.72.439-Release ... FAILED (invalid public key 8FD3D9A8D3800305A9FFF259D1742AD60D811D58)
==> ERROR: One or more PGP signatures could not be verified!
 -> error downloading sources: spotify 
     context: exit status 1 

Maybe Kpcyrd and Foxboron got permission to ship Spotify, which they can't because of trademarks, directly from the Spotify Devs/Managers/Owners. Or maybe not... Probably it was only a test.

For reference in January 2020 they were at 36C3 and got permission to ship Signal from Moxie, and then the package was added to community repo. Reddit thread on that: https://www.reddit.com/r/archlinux/comments/emdm6e/arch_linux_now_ships_signaldesktop/fdnyaoo/

https://github.com/archlinux/svntogit-community/commit/5ac9e51da28a1f4dc7eb02f46245203779954550#diff-3e341d2d9c67be01819b25b25d5e53ea3cdf3a38d28846cda85a195eb9b7203a Interesting. There was one, yes.

Here is the info from the pkg, sorry for the greek language, but it says kpcyrd created it

Όνομα : spotify Έκδοση : 1:1.1.72.439-2 Περιγραφή : A proprietary music streaming service Αρχιτεκτονική : x86_64 URL : https://www.spotify.com Άδειες : custom Ομάδες : Ουδέν Παρέχει : Ουδέν Εξαρτάται από : alsa-lib>=1.0.14 gtk3 libxss desktop-file-utils openssl nss at-spi2-atk libcurl-gnutls libsm Προαιρετικές εξαρτήσεις : ffmpeg-compat-57: Adds support for playback of local files zenity: Adds support for importing local files [εγκατεστημένο] libnotify: Desktop notifications [εγκατεστημένο] Απαιτείται από : Ουδέν Προαιρετική εξάρτηση σε : Ουδέν Διένεξη με : Ουδέν Αντικαθιστά : Ουδέν Μέγεθος εγκατάστασης : 279,01 MiB Υπεύθυνος πακέτου : kpcyrd kpcyrd@archlinux.org Ημερομηνία δημιουργίας : Κυρ 05 Δεκ 2021 01:50:35 μμ EET Ημερομηνία εγκατάστασης : Κυρ 05 Δεκ 2021 02:11:08 μμ EET Αιτία εγκατάστασης : Ρητώς εγκατεστημένο Σενάριο εντολών εγκατάστασης : Όχι Επικυρωμένο από : Υπογραφή

@TemplarGR Huh, that's interesting. It definitely wasn't "spotifyd"?

There was for a little while. It upgraded to same version but pkg version 2. Then it got dropped from the community repo again. NOW there isn't. But it is still installed on my system....

@TemplarGR There is no Spotify in the community repo.

Today i updated this from the community repo and after a while it got dropped again. What is happening with this package?

change the line #40 to : validpgpkeys=('F9A211976ED662F00E59361E5E3C45D7B312C643') # Spotify tux@spotify.com

To do what @fabiscafe commented, but on 'yay' do this:

# Import the new key
curl -sS https://download.spotify.com/debian/pubkey_5E3C45D7B312C643.gpg | gpg --import -

# delete old key
gpg --delete-key D1742AD60D811D58

# run yay and edit PKGBUILD
yay -Syu --editmenu spotify

# It will promt:
=> PKGBUILDs to edit
# Edit [A]ll
# change
pkgrel = 1
# to
pkgrel = 2

# change
8FD3D9A8D3800305A9FFF259D1742AD60D811D58
# to
F9A211976ED662F00E59361E5E3C45D7B312C643

# exit the file and follow yay as per usual

For real.. just use the Spotify flatpak. But if you don't want to you can also do this until the PKGBUILD is up-2-date again:

#import new key
curl -sS https://download.spotify.com/debian/pubkey_5E3C45D7B312C643.gpg | gpg --import -

#delete old one (optional)
gpg --delete-key D1742AD60D811D58

#clone Repo
git clone https://aur.archlinux.org/spotify.git

#move into git-repo-dir
cd spotify

#update PKGBUILD with new key and new pkgrel
sed -i 's/8FD3D9A8D3800305A9FFF259D1742AD60D811D58/F9A211976ED662F00E59361E5E3C45D7B312C643/;s/pkgrel=1/pkgrel=2/' PKGBUILD

#build and install
makepkg -scCri

Have fun.

Tried to install this today. I am also getting the pgp error. After I learned that the pgp key has changed, I used the pgp key @Rota commented below. Sadly this did not help for me. I now get: spotify-1.1.72.439-Release ... FAILED (invalid public key F9A211976ED662F00E59361E5E3C45D7B312C643) ==> ERROR: One or more PGP signatures could not be verified!

new gpg: https://download.spotify.com/debian/pubkey_5E3C45D7B312C643.gpg

new GPG key

marking out of date

Honestly there's so many issues with this package through the years that I've moved to the flatpak version and I'm having zero issues there, apart from the window title icon and window title not showing, which seems to be a bug with Spotify rather than the package itself obviously.

Maybe that helps someone else as well.

Looks like Spotify have updated their GPG key again, but they don't seem to have made the public key available.

Currently trying to install this package gives me the error:

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

gpg -k 0D811D58 tells me that the old key is set to expire on the 2nd of December, so it makes sense that they've updated the key. However speculatively trying to download https://download.spotify.com/debian/pubkey_B312C643.gpg gives me a 403 Forbidden error.

Therefore until they make their new public key actually public, this package cannot be installed without skipping signature checks.

@george.fst Thank you for mentioning that this is a Spotify button. I was confused because there is no fullscreen button in the bottom right like everyone else is saying.

Turns out, this a Premium feature. Looks like I've got to go digging through xpui.js again to see if there is a way to enable it for free users if I want a working titlebar.

Thanks @udalov, that also works on XFCE, so I think we can fairly safely say it works universally.

(I did initially think you meant some KDE-specific fullscreen button, not realising that Spotify has it's own notion of fullscreen)

@udalov Thanks for the workaround. Working on my KDE Archlinux too. Odd problem indeed.

@udalov Thank you for that. Works with MATE also. Nice workaround for now.

I found a workaround for the X11 icon in the task switcher issue which works for me on KDE. Click "Full screen" at the bottom-right corner, and optionally click it again to return to the normal mode. The icon becomes the normal Spotify icon.

The new release can't be built due to GPG errors:

==> Verifying source file signatures with gpg... spotify-1.1.72.439-Release ... FAILED ==> ERROR: One or more PGP signatures could not be verified!

thx @NicoHood libGLESv2.so fix <3

==> Extracting sources... -> Extracting spotify-1.1.68.632-x86_64.deb with bsdtar ==> Starting prepare()... spotify-1.1.68.632-x86_64-Packages: OK spotify-1.1.68.632-x86_64.deb: FAILED sha512sum: WARNING: 1 computed checksum did NOT match ==> ERROR: A failure occurred in prepare(). Aborting...

Has someone fixed the X11 icon problem yet?

I am having the same issue as @nihakuto, deleting the .config/spotify directory doesn't change the "Something went wrong" screen. Edit: restarting seems to have resolved it!

Still seeing an "X11" icon. Also, launching it now takes 5-10 seconds. It stays with a black screen. And every time I login, I'm getting an error about a "firewall". Tho i don't have any firewall installed or enabled.

For me the icon is only missing from the workspace switcher (all other maximized windows show their icon, except spotify). Spotify icons in the menus and my window lists or dock are all ok. tried to delete the ~/.config/spotify with no change. MATE desktop.

Hi, I'm getting an "X11" logo instead of the Spotify one. Also, it's not showing in application menu every time I check it on multimedia > ... Does any one knows how to fix this?

@mcmarius11 Deleting ~/.config/spotify did not solve the icon problem for me. Did anybody's?

just delete the .config/spotify folder in your home directory, this fixed the problem for me :)

@francoism90 Similarly on XFCE, I get the default window icon.

Weirdly the spotify icon sometimes shows up after a few hours. And always shows up for a split second when I close the window.

@francoism90, I get the same thing. X11 logo in the window bar, and the text is stuck saying "Spotify" and doesn't change to the current song. It seems to be a bug in these past few versions of Spotify. I think we'll have to wait until an update fixes it.

I'm getting an 'ugly' X11 as window application icon on KDE Plasma. Is this normal? Any workarounds, like force running Spotify under Wayland (if possible)?

I had the same problem with blank Spotify window and prints

spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by spotify)

What fixed "blank window" for me was system upgrade. However I still see the prints about libcurl, so I'd presume they're harmless and unrelated to blank Spotify window.

I also get the no information available error plus this:

libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)

I'm currently getting this when trying to start Spotify.

% spotify
spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)

Not sure how to fix this. It also just doesn't display the Spotify window at all, although I seem to be able to play music if I control it via MPRIS. This is using X11 and i3. It worked like a day or whatever ago before I posted this. I installed the flatpak package instead and that seems to work better (although that doesn't set a window title, which is annoying for me as an i3 user, but that's a separate issue).

@TJM: update coreutils to 9.0-2. The fix for the issue with chmod was backported in this version :)

https://github.com/archlinux/svntogit-packages/commit/f6e08690bc11a243918d5416558f48426bfb1f8e

makepkg reports an error:

==> ERROR: A failure occurred in package().
    Aborting...

Which seems that chmod -R go-w "${pkgdir}" returns 1.

@Namarrgon - I understand. Thank you for the explanation, and it makes perfect sense.

I'm not saying that you should switch to the testing repos, update only the coreutils package. The patch in $pkgrel -2 concerns only chmod and doesn't interact with anything else in the repos. Partial updates are bad but in this case the risk is manageable.

@Namarrgon, I'm going to say something critical, and therefore feel compelled to say thank you for maintaining this clearly challenging package!!!! I love using it, and really appreciate having it available.

That said, I'm not a fan of required packages from testing - I almost never enable testing and, having to do so for this single package seems excessive. As hacky as the solution is from @rigelbm, the pattern has less of a blast radius than pulling in the fixed chmod from testing because it's only modifying the current package, as opposed to changing the state of the package management system. Would you mind walking me through your reasoning for the path you took?

Update to coreutils 9.0-2 that is currently in [testing], it has a fix for chmod.

My solution to this problem was to replace the unconditional chmod with a find, to exclude all links.

find "${pkgdir}" ! -type l -exec chmod go-w {} +

What happens if 'chmod -R go-w "{pkgdir}"' is changed to 'chmod go-w "{pkgdir}"'? It seems to work for me

@NicoHood, try find "${pkgdir}" -type f -exec chmod go-w {} +. It worked for me. That should make chmod be applied only to the files (non-symlinks).

Okay makes sense now! Isnt there an option in coreutils to ignore symlinks?

If we ignore the error, aka || true, will chmod still finish and modify all other files or will it stop after the error?

@NicoHood the chmod behaviour has just changed between coreutils 8.32-1 and 9.0-1. Check you have 9.0-1 installed then do a clean build. This change is affecting multiple other packages (e.g. mailspring).

I cannot really follow you discussions about chmod. Why does it fail? For me it works perfectly since years. Was there a recent change in the debian file? But if so my local build would also fail, so I dont see where you guys have problems.

Removing chmod -R go-w "${pkgdir}" is a problem since files would be installed with too wide permissions.

The problem is the (changed?) behaviour of chmod:

chmod never changes the permissions of symbolic links; the chmod system call cannot change their permissions. This is not a problem since the permissions of symbolic links are never used. However, for each symbolic link listed on the command line, chmod changes the permissions of the pointed-to file. In contrast, chmod ignores symbolic links encountered during recursive directory traversals.

In this case bin/spoitfy points to /opt: pkg/spotify/usr/bin/spotify -> /opt/spotify/spotify but chmod does not have permissions to modify /opt.

$ chmod  go-w  pkg/spotify/usr/bin/spotify; echo $?
chmod: changing permissions of 'pkg/spotify/usr/bin/spotify': Operation not permitted
1

But still the permissions of all other files need to be changed. I suggest instead to add chmod -R go-w "${pkgdir}" || true to never fail on chmod as the cheapest workaround.

To fix ==> ERROR: A failure occurred in package(). Aborting...

just remove -R from

chmod -R go-w "${pkgdir}"

at the end of PKGBUILD.

One more person that was able to install by downgrading to core utils 8.32-1, pacman -U https://archive.archlinux.org/packages/c/coreutils/coreutils-8.32-1-x86_64.pkg.tar.zst

I have a question though, @zapata, I'm using paru and I didn't get any proper error message. How were you able to debug the issue aka discover the line causing the error?

I only got this:

==> ERROR: A failure occurred in package().
    Aborting...
error: failed to build 'spotify-1:1.1.68.632-1': 
error: packages failed to build: spotify-1:1.1.68.632-1

Thanks for the info! That makes sense.

People like you are part of what makes the Arch community so great :)

spotify-snap was created because the deb version (this one) was outdated and not getting updated by Spotify, while the snap was getting updated. As a fix, spotify-snap was created so that we could get updates to Spotify by using the Snap version. Since this version is now up to date and at the same version as the snap package, spotify-snap isn't necessary anymore.

@Techcable

I didn't want to say anything about it here. But since you brought it up :-D

This is what I wrote as a request to the AUR team.

There was a short time where this package made sense. Since Spotify provides up-to-date Debian packages in their repository again. This package is obsolete.

The same is true for spotify-edge-snap

The spotify package is maintained by a trusted user. I cannot compete with that and I don't see any reason why I should.

So it got removed shortly afterwards

Out of curiosity, what happened to the spotify-snap package?

Thanks, @zapata. I also ran into the same issue today when I tried to upgrade my Spotify from 1.1.68.628-1. Downgraded coreutils back and the package was made successfully. I assume I can go ahead and upgrade coreutils back to latest?

Suddenly I can no longer install spotify:

==> ERROR: A failure occurred in package(). Aborting...

The command 'chmod -R go-w "${pkgdir}"' fails. The command works if I run it manually. But echo $? returns 1.

Sorry, this is a problem with coreutils. Downgrading to 8.32-1 or patching resolves the issue. https://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=e8b56ebd5

Hi @NicoHood can you watch this topic please? https://bbs.archlinux.org/viewtopic.php?id=269788 And possibly propose an alternative to the resolution of this problem. Thank you very much

http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.68.628.geb44bd66_amd64.deb is 404, that's why it's failing

my ghetto fix for now was editing the build files to the previous version (https://repository-origin.spotify.com/pool/non-free/s/spotify-client/) also skipping the hash check below, here's a pastebin with what I changed: https://pastebin.com/y4F4KTj9

couldn't download package, installed using @szuk's method.

==> ERROR: Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.68.628.geb44bd66_amd64.deb Aborting...

just got it when trying to update

Hello everyone,

since most of us are running into the same problem, I've decided to post a short workaround here until this gets resolved officially by the package maintainer.

I'm using yay as a package manager.

Here are the following steps.

1. yay -G spotify

2. edit the PKGBUILD with opening your favorite editor ... path should be something like this: $HOME/.cache/yay/spotify/PKGBUILD

3. makepkg -si

fin.

 ==> Starting prepare()...
 spotify-1.1.68.628-x86_64-Packages: OK
 spotify-1.1.68.628-x86_64.deb: FAILED
 sha512sum: WARNING: 1 computed checksum did NOT match

I just commented out the sha512sum commands in the PKGBUILD prepare() before installation. This works but is not ideal i guess:p

Diff from 1.1.68.628 to 1.1.68.632

diff --git a/PKGBUILD b/PKGBUILD
index 4ce30cf..cd2e519 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -4,9 +4,9 @@
 # Contributor: Eothred <yngve.levinsen@gmail.com>

 pkgname=spotify
-pkgver=1.1.68.628
+pkgver=1.1.68.632
 epoch=1
-_commit=geb44bd66
+_commit=g2b11de83
 pkgrel=1
 pkgdesc='A proprietary music streaming service'
 arch=('x86_64')
@@ -33,7 +33,7 @@ source=('spotify.protocol'
         "${pkgname}-${pkgver}-x86_64-Packages::http://repository.spotify.com/dists/testing/non-free/binary-amd64/Packages")
 sha512sums=('999abe46766a4101e27477f5c9f69394a4bb5c097e2e048ec2c6cb93dfa1743eb436bde3768af6ba1b90eaac78ea8589d82e621f9cbe7d9ab3f41acee6e8ca20'
             '2e16f7c7b09e9ecefaa11ab38eb7a792c62ae6f33d95ab1ff46d68995316324d8c5287b0d9ce142d1cf15158e61f594e930260abb8155467af8bc25779960615'
-            'aa21e1becf03fb1d2e13d5f706f6e6cba877ea8d93540fef94ebeac1186e5a029cbd2fffcae65d801863dc3523de3ff0b32b1fb6aa40bfe59ac076cbb1cd0dc7'
+            '742bf459d7d87cc269a4c29cd2489753c6f7b62f3ee2150808c4931c29ee0d89f5b5ae47589112768e5958da73cba857074845fd017bd53c4574ea84c6770074'
             'SKIP'
             'SKIP'
             'SKIP')

md5sum error

Same problem ¨The deb file's sha512sum doesn't match¨

The deb file's sha512sum doesn't match

@NicoHood: I already had that key imported, but now I deleted 2 of his previous (outdated) keys and THEN it worked:

gpg --delete-keys 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90
gpg --delete-keys 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45

@madjoe: You are missing the public key needed for authenticating the .sig file. You can either skip the gpg check using

makepkg --skippgpcheck

or, to be on the secure side, import the public key of tux@spotify.com

gpg --recv-keys 8FD3D9A8D3800305A9FFF259D1742AD60D811D58

(You can check if the key is valid by comparing to the key that the PKGBUILD expects)

EDIT: See also the pinned comment:

curl -sS https://download.spotify.com/debian/pubkey_0D811D58.gpg | gpg --import -

to manually import

@NicoHood: I'm still getting the same PGP error. How to fix it?

@NicoHood thanks. That's awesome. I did not know about that, it just shows how you can get stuck in old stupid way of doing things. Thank you very much :)

@Biologos that is a great idea. We could use a wrapper script, that checks the environment variable. The question is: Is there a common name for such a variable?

Cause then we dont need multiple dektop files.

Edit: Did you try: https://wiki.archlinux.org/title/HiDPI#GDK_3_(GTK_3) ? Maybe it already works?

Did you also check https://wiki.archlinux.org/title/HiDPI#Skype ?

Would it be possible to add few lines to pkgbuild to automatically create .desktop file with Exec=spotify --force-device-scale-factor=1.5 %U?

For example a global variable if not set --force-devide-scale-factor would not be present in built package if set it would use its value as value for this parameter.

I mean it is just a small improvement for my life. As currently every single update I have to manually edit the .desktop afterward because I have 27'' 4K display and Spotify is unusable with scaling lower than 1.5.

spotify-1.1.68.628-Release ... FAILED
==> ERROR: One or more PGP signatures could not be verified!

@alosarjos, I can confirm the album art is fixed for me. I can see the album art being displayed in my Media Player panel. However, I use KDE Plasma, not Gnome.

Gnome user here. Is the album image showing for anyone on the MPRIS controls to anyone? It's supposed to be fixed but I can't still see it.

https://www.omgubuntu.co.uk/2021/09/spotify-linux-client-finally-fixes-missing-artwork-bug-improves-speed

Can confirm @szuk's comment fixes the problem. Hopefully maintainers can become as smart as them.

Hi,

I get sha512sum fail as well:

potify-1.1.67.586-x86_64.deb: MISSLYCKADES sha512sum: VARNING: 1 beräknad kontrollsumma stämde INTE ==> FEL: Ett fel uppstod i prepare(). Avbryter... error making: spotify

I tried the patch mentioned in the comments but get errors

2 out of 2 hunks FAILED -- saving rejects to file PKGBUILD.rej

Tried installing spotify again but I get the same checksum error

Thank you Sanras!! My mistake obvioulsy. Still it remains that this package is a pain ^^

personaly I switched to the snap package. no headache

@benedict_0, do you have base-devel package group installed on your system?

Thank you szuk, it looked promising but it exited on: ==> ERROR: Cannot find the fakeroot binary.

For those having trouble with the AUR package being out of date, try this:

• Download this package's PKGBUILD (with yay, run yay -G spotify).
• Navigate to the directory containing the PKGBUILD file, and open it in your preferred editor.
• Find these two lines in the file:

pkgver={version string}
commit={commit hash}

• Navigate to https://repository-origin.spotify.com/pool/non-free/s/spotify-client/.
• Locate the file in the list with the latest version number. It should be of the format "spotify-client_{version string}.{commit hash}_amd64.deb".
• Replace the lines you found earlier with the corresponding values in the file name. Save the file.
• From the terminal, in the directory of the PKGBUILD file you just edited, run updpkgsums, followed by makepkg -si.
• Spotify should install properly. If you wish, you can remove the directory the PKGBUILD file was contained in.

The prepare() .deb sha512sum check fails again for pkgver 1.1.67.586-1.

The reports for the previous versions didn't get an answer for how to fix it. I'm going to just skip the check for now?

Like Sanras, I've also encountered a bug with the window title not being set with the most recent update.

I also had the "firewall" issue. All songs were grayed out and after reinstall, I could not log in. The message was "A firewall may be blocking spotify [...] error code: accesspoint:34" Running spotify with the --show-console option shows that it tries to use the NetworkManager. In my case, NetworkManager was not running, so no package left my PC. Starting NetworkManager solved this issue for me. I'm not sure if it's a corner case, but maybe we should include NetworkManager in the depedencies.

when will spotify support the tray icon again?? it's incredible that before spotify had a qt version with tray icon and not now.. i'm with deezer now that is not native at all but it works like spotify... and I am testing spotify qt legacy version that is 2017 versioned in aur JAJAJ But it's awesome, may be we will have to " put " another thread with that situation, it's horrible to not to have tray icon here :(

Just noticed that the latest version doesn't change the window title to the playing song. Quite annoying. Is this intended behavior, or a bug?

Edit - Definitely a bug. The title bar somehow changed from the X11 logo to the Spotify one (as its supposed to be), and the song that was playing at the time is displaying as the title. However, it just happened this one time for some reason. The title still doesn't update with new songs playing, so it seems it was just a fluke that the titlebar updated correctly for one of the songs.

I can't believe it. MPRIS actually works now. I thought it would take Spotify at least another decade to fix this, but I'm impressed by how fast they fixed this issue. It only took a couple years!

They've managed to pull blurred album arts on any zoom scale, and added annoying sliding animation when picking a track from a list!

The deb file is working again.

mpris seems ok here: using for song info and play/pause/stop/forward/back controls

Can somebody please test if the mpris feature now works again?

Wrote a patch file to update the spotify package

diff --git a/.SRCINFO b/.SRCINFO
index ce60133..c0f8074 100644
--- a/.SRCINFO
+++ b/.SRCINFO
@@ -1,6 +1,6 @@
 pkgbase = spotify
    pkgdesc = A proprietary music streaming service
-   pkgver = 1.1.56.595
+   pkgver = 1.1.67.586
    pkgrel = 1
    epoch = 1
    url = https://www.spotify.com
@@ -21,17 +21,16 @@ pkgbase = spotify
    options = !strip
    source = spotify.protocol
    source = LICENSE
-   source = spotify-1.1.56.595-x86_64.deb::http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.56.595.g2d2da0de_amd64.deb
-   source = spotify-1.1.56.595-Release::http://repository.spotify.com/dists/testing/Release
-   source = spotify-1.1.56.595-Release.sig::http://repository.spotify.com/dists/testing/Release.gpg
-   source = spotify-1.1.56.595-x86_64-Packages::http://repository.spotify.com/dists/testing/non-free/binary-amd64/Packages
+   source = spotify-1.1.67.586-x86_64.deb::http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.67.586.gbb5ef64e_amd64.deb
+   source = spotify-1.1.67.586-Release::http://repository.spotify.com/dists/testing/Release
+   source = spotify-1.1.67.586-Release.sig::http://repository.spotify.com/dists/testing/Release.gpg
+   source = spotify-1.1.67.586-x86_64-Packages::http://repository.spotify.com/dists/testing/non-free/binary-amd64/Packages
    validpgpkeys = 8FD3D9A8D3800305A9FFF259D1742AD60D811D58
    sha512sums = 999abe46766a4101e27477f5c9f69394a4bb5c097e2e048ec2c6cb93dfa1743eb436bde3768af6ba1b90eaac78ea8589d82e621f9cbe7d9ab3f41acee6e8ca20
    sha512sums = 2e16f7c7b09e9ecefaa11ab38eb7a792c62ae6f33d95ab1ff46d68995316324d8c5287b0d9ce142d1cf15158e61f594e930260abb8155467af8bc25779960615
-   sha512sums = 4a270461d07c339a3fdf49cd0a8728d4fc7300be001a1ba59c74f05bf273b79a61bde6d046c27a6af38dfb6af58963fbd8b8cd7468c91b91e48b0d32b3dcc2b5
-   sha512sums = SKIP
-   sha512sums = SKIP
+   sha512sums = d105eed1f013be2704ad7f0aaeb80ab2f8f19a0cfe69782f32fc95241d2900560996ec17101222365e1ad3b02ff9fa866da3f0709277a5bb40d032f5a58f7062
+   sha512sums = cca38e691ed71b1a2e3c8edef9b09dd3244403663830391e3acf4e062da523cb690e9cbb6de5f177d3ab4d12e61f52d073aa516d38d2b4cff2f48b2871cab2f3
    sha512sums = SKIP
+   sha512sums = c02ff159798a9d0ca7f2774bf621c7973ac0ed6fbf0c6839d3e45fb99cb3441436e966ff3d4a34e2b1bd8ccb32fbb0174f6a79c5a9c46ebb357a1501557fb087

 pkgname = spotify
-
diff --git a/PKGBUILD b/PKGBUILD
index 7102488..9a4ad41 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -4,9 +4,9 @@
 # Contributor: Eothred <yngve.levinsen@gmail.com>

 pkgname=spotify
-pkgver=1.1.56.595
+pkgver=1.1.67.586
 epoch=1
-_commit=g2d2da0de
+_commit=gbb5ef64e
 pkgrel=1
 pkgdesc='A proprietary music streaming service'
 arch=('x86_64')
@@ -31,12 +31,13 @@ source=('spotify.protocol'
         "${pkgname}-${pkgver}-Release::http://repository.spotify.com/dists/testing/Release"
         "${pkgname}-${pkgver}-Release.sig::http://repository.spotify.com/dists/testing/Release.gpg"
         "${pkgname}-${pkgver}-x86_64-Packages::http://repository.spotify.com/dists/testing/non-free/binary-amd64/Packages")
+
 sha512sums=('999abe46766a4101e27477f5c9f69394a4bb5c097e2e048ec2c6cb93dfa1743eb436bde3768af6ba1b90eaac78ea8589d82e621f9cbe7d9ab3f41acee6e8ca20'
             '2e16f7c7b09e9ecefaa11ab38eb7a792c62ae6f33d95ab1ff46d68995316324d8c5287b0d9ce142d1cf15158e61f594e930260abb8155467af8bc25779960615'
-            '4a270461d07c339a3fdf49cd0a8728d4fc7300be001a1ba59c74f05bf273b79a61bde6d046c27a6af38dfb6af58963fbd8b8cd7468c91b91e48b0d32b3dcc2b5'
-            'SKIP'
+            'd105eed1f013be2704ad7f0aaeb80ab2f8f19a0cfe69782f32fc95241d2900560996ec17101222365e1ad3b02ff9fa866da3f0709277a5bb40d032f5a58f7062'
+            'cca38e691ed71b1a2e3c8edef9b09dd3244403663830391e3acf4e062da523cb690e9cbb6de5f177d3ab4d12e61f52d073aa516d38d2b4cff2f48b2871cab2f3'
             'SKIP'
-            'SKIP')
+            'c02ff159798a9d0ca7f2774bf621c7973ac0ed6fbf0c6839d3e45fb99cb3441436e966ff3d4a34e2b1bd8ccb32fbb0174f6a79c5a9c46ebb357a1501557fb087')
 validpgpkeys=('8FD3D9A8D3800305A9FFF259D1742AD60D811D58') # Spotify <tux@spotify.com>
 # Old Keys:
 # 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90

Save this to a file, you can call it patch.patch Put this file in the root directory of this package, spotify/ and do patch -p1 < patch.patch

Deb file doesn't exist anymore.

curl: (22) The requested URL returned error: 404
==> ERROR: Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.56.595.g2d2da0de_amd64.deb
    Aborting...

Hi,

I get sha512sum fail as well:

==> Starting prepare()...
spotify-1.1.56.595-x86_64-Packages: OK
spotify-1.1.56.595-x86_64.deb: FAILED
sha512sum: WARNING: 1 computed checksum did NOT match
==> ERROR: A failure occurred in prepare().
    Aborting...
error making: spotify

sha512sum fail on installation.

Hi,

I really hate to mention what worked for me. I am using OpenDNS on my router, changing to my ISPs DNS servers makes Spotify work atleast for me. No qt4 or whatever installed to make it work.

Starting to believe that its always DNS...

@greenfuse Thanks! I can confirm this works on Manjaro. It didn't fix itself but after I installed qt4-bin and did a reboot, it started working again.

@greenfuse fair enough, I see you already opened an issue there. :-) Edit: Must say I am really disappointed in spotify pretty much refusing to help fixing any linux-client problems. Same goes to the Cisco Webex client

It worked and I am posting as it might help others. Not saying it makes sense. Who knows what qt4 or any of its components has to do with this unsupported proprietary software that was developed in the engineers' spare time. For all I know it was just coincidental timing if it is now working again for everyone.

Playing songs works again for me (without reinstall or installing anything else). Seems like they fixed the issue on their side :)

I don't see how that would solve any problems. spotify uses GT3 for graphics (at least the official version). Greyed out songs sound more like a bug (or unintended feature?) than a missing dependency. I would recommend checking out the forum for problems regarding the application: https://community.spotify.com/t5/Desktop-Linux/bd-p/desktop_linux

All songs were greyed out and I was unable to play. Resolved by installing qt4 (qt4-bin on my other device).

@cars10 there is no aditional output when you try to play an online song?

if you guys get the "not possible to play atm" message, than start spotify in terminal to read the output. i suspect it is pulseaudio related since I don't use it and Spotify is working here

When starting spotify i get the following errors, not sure if this is related to the current inability to play songs:

spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)

@jharch Yeah I'm hoping for the same. Tried reinstalling it but in vain.

@systemofapwne Yeah, I was getting the same message when I first encountered the problem and tried logging in again. However, after reinstalling it, I don't get the same message. I can log in normally and play the offline songs. The unavailability issue still persists.

It still works for me

I can confirm, that out of nowhere, the songs are unavailable as of today. Logging out and trying to log-in again, I get an error message: "A firewall may be blocking Spotify."... "Error code: accesspoint:39". Setting a proxy for Spotify also did not help. The browser-version still works.

I believe this to be a bug on spotifiy's side, I've had the same problem on my Android phone as well as my PC for numerous times, I also know friends of mine also complaining about that issue on their phones. Most of the times it just goes away after a while.

Out of nowhere, all the songs in any of the online playlists are being shown as unavailable. I tried toggling the offline mode but in vain. Only my saved offline songs are playable. I looked at upstream forums where the marked solution is toggling the offline mode but as aforementioned, that didn't work for me. Anyone else facing the same problem?

Any help will be appreciated. Thanks in advance!

I've recently had high cpu-usage when listening on songs on Spotify. It goes up to around 50% on my 4770k, and only when actually playing -- not when pausing. Does anyone else have this problem?

Is the loudness normalization working for you guys? mine seams to be stuck at the loud setting (-11LUFS)no matter what I choose in the settings. or it is off, but I meassure -11LUFS for most songs

EDIT: loudness on/off is working if restarting the app, but loudness level will always be "loud", even if putting on "silent"

Interesting -- thanks, @NicoHood, you are right, and it does play songs even without ffmpeg-compat-57 and my playback problems are related to something else ("No network and no cached capability"). I will try to debug further and report back, probably related to ZFS like someone mentioned below.

Whenever I want to start spotify, I get the following error (when run from terminal): error: app/com.spotify.Client/x86_64/master not installed

Installing ffmpeg-compat-57 does not change this. Any idea what this means?

@daroczig it definitely works without for me. Can you please check the following:

Uninstall ffmpeg with all not required dependencies: sudo pacman -Rs ffmpeg-compat-57

Install it again, but check the output which additional dependencies are pulled in.

Maybe one of the dependencies is required, not ffmpeg itself.

Could you please also test if the "normal" ffmpeg works for you when ffmpeg-compat-57 is not installed?

I can confirm that ffmpeg-compat-57 might be a required package -- without that, I was not able to play any song in the Spotify client: it was throwing a lot of network-related (e.g. No network and no cached capability) errors when running with the --show-console flag. After installing ffmpeg-compat-57, all these errors (and complains about being offline) were gone and I could play songs again.

@rubycasey I did not try local files, but I can play "normal" online songs. Maybe it is required to install ffmpeg (without compat)? Cause I have installed that.

@rubycasey Somehow I'm having the opposite experience. Even without ffmpeg-compat-57 I can still play local files (as well as remote).

Just wanted to comment that I don't think ffmpeg-compat-57 is just an optional dependency anymore. Without it I am unable to play any songs in the app at all (not just local files anymore).

@NicoHood Run this with spotify open and some song loaded:

qdbus org.mpris.MediaPlayer2.spotify /org/mpris/MediaPlayer2 org.mpris.MediaPlayer2.Player.Metadata

If mpris:artUrl contains the new hostname i.scdn.co, this means the bug is probably somewhere in GNOME (I found this, maybe related). I'm on KDE and it works just fine.

EDIT: Just realized something, the notifications on song change are generated by Spotify, and they worked for me even before applying this patch (MPRIS isn't involved). The album art was missing only with the MPRIS clients, in my case, the KDE Media Center in the system tray. So I guess your issue is the GNOME bug I linked previously. You can probably use some other MPRIS client for GNOME to verify that at least this patch is doing its job.

@iamkroot The patch gets applied correct, but in my gnome notifications there is still no Icon. Maybe there is another issue, I am not sure if that works with MPRIS?

@NicoHood it is indeed very hacky and can break at any time - we're just fortunate that the new hostname is shorter so we can simply patch it in-place.

I haven't messed with the PKGBUILD yet, I simply ran the command on my installed binary. What exactly do you mean when you say it isn't working when you add the command to the PKGBUILD? Is it not applying the patch, or is the album art still not showing up?

You can verify that the string was replaced by running:

strings -t d /opt/spotify/spotify | grep i\.scdn

I get the replaced string at offset 604094 and after restarting the app, album art shows up as expected.

@iamkroot okay this looks super hacky. I've tried to apply the patch inside the PKGBUILD but it does not work. I've used:

sed -i 's/https\:\/\/open\.spotify\.com\/image\/\%s/https\:\/\/i\.scdn\.co\/image\/\%s\x00\x00\x00\x00\x00\x00\x00/g' "${pkgdir}"/opt/spotify/spotify

Any ideas from your side?

In case someone is looking to get the album art working in MPRIS, I found this on r/kde:

sudo sed -i 's/https\:\/\/open\.spotify\.com\/image\/\%s/https\:\/\/i\.scdn\.co\/image\/\%s\x00\x00\x00\x00\x00\x00\x00/g' $(where spotify | xargs realpath)

Might be nice to have a patch file for this.

@OJFord would you mind checking, if that tip already exists in the wiki? You might want to add it, if not. Sounds like a good tip! https://wiki.archlinux.org/title/Spotify

I have found the cause of that 'something went wrong' and refusal to start (after realising there's a --show-console flag with much more logging): Spotify uses LevelDB for its cache, which does not support (its files being inside) FUSE filesystems. https://github.com/google/leveldb/issues/211

My XDG_CACHE_HOME is within such a filesystem because I use gocryptfs to encrypt my home directory (or more to the point, to decrypt and mount it on login).

Work-around is to symlink it to somewhere else; since it's just a cache I'm using /tmp/spotify. Slight gotcha is that the symlink won't be dereferenced when checking if the dir needs to be created, so wherever you put it make sure it always exists.

For the last several days (perhaps since 27 May update to libcurl-gnutls? Untested) I've had 'something went wrong, try reloading the page' on start; reloading doesn't fix it, so it's completely unusable.

journalctl:

rofi[19169]: spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by spotify)
rofi[19174]: /opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
rofi[19173]: /opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
bluetoothd[463]: Player registered: sender=:1.16 path=/_1_3487
bluetoothd[463]: profiles/audio/media.c:parse_int64_metadata() expected DBUS_TYPE_INT64 got DBUS_TYPE_UINT64
rofi[19197]: /proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)

which.. I'm not sure is the problem.

I get the same launching from command line instead of using rofi, and the same after fully uninstalling, clearing its cache and user config, and reinstalling: the login page then loads, but this error comes after successful login. The web player works fine, so I don't think it's network related.

Does anyone else have this issue? Found any work around or tried downgrading libcurl-gnutls? (I probably will get around to that at some point, making do with web player for now.)

idk if this has been mentioned yet. But an alternative for fixing the download problem is to just run the yay command again and again until it finishes. The downloader will resume from where it left off so it will eventually work. Only took 2 times for me. This is just the lazy person's solution :)

@tar3k That is not correct. yay -Syu will update all packages, including AUR, community, extras, base, etc, whereas yay -Sua only updates AUR.

From the man page:

yay -Syu
    Update package list and upgrade all currently installed repo and AUR.

yay -Sua
    Update all currently installed AUR packages.

I use yay -Syu and it will update packages and let me know if any AUR package is out of date as well.

@tobfromme to update all the AUR packages through yay you need to run yay -Sua. It will also show you if any package got flagged out of date.

Does anyone use yay? All you need to do with that is continue running yay -Syu just like pacman and it will eventually complete.

Just curious, not trolling or flaming. To each their own. :)

pamac build spotify

Choose e to edit build files. Add this line to PKGBUILD

DLAGENTS=("http::/usr/bin/wget -r -np -nd -H %u")

Save and apply transaction. Good luck!

Local files playback works without ffmpeg-compat-57, even though deb package "recommends" artifacts from it.

@willquill

No, don't use pamac/paman for that. Simply overriding the DLAGENTS on the PKGBUILD solves the issue. I didn't test yet if adding --retry to curl is enough, but I had success with wget.

I was able to resolve the download issue by using the --hotedit feature of my AUR helper (Aura) to edit the PKGBUILD, and add the following line:

DLAGENTS=("http::/usr/bin/wget %u")

Which causes it to use wget (must be installed on your system) to download the file. Wget successfully retries and resumes the download to cope with whatever their server is up to.

Is anyone else getting download issues for the .deb file? It would start to download, but around the ~23mb mark it would error out with a Network Error no matter how many attempts have been made.

Yes. The workaround is to open the Pamac GUI, search "spotify 1:1.1.56.595-1" and install through the GUI. My 'paman build spotify' was also having download issues.

@cartesius

Not needing to install flatpak.

What are the benefits of runing this AUR package vs. the flatpak version of Spotify?

@grazzolini: Yes, I've also noticed exactly that.

Ever since a couple of versions ago I have been having issues to download the .deb file. The server will cut the download at various points. I've switch to using wget on DLAGENTS, because it does handle retries (I guess curl's --retry should do it too), but I have been wondering if more people have been having this issue.

It is a beta program with random opt-in. I also got the new interface on both PCs where I am running Spotify.

@shillshocked

I think the new interface is server side. My spotify install hasn't updated since March 27 and I have the horrible UI, so it must be partly server side.

Edit: confirmed is server side https://www.reddit.com/r/spotify/comments/mnd3hv/the_new_ui_update_is_unacceptable/

The new update to Spotify is utterly garbage. It completely gimps the interface and takes away many crucial features. Any way to downgrade? The deb files referenced by the old pkgbuild no longer exist on the main site, but they are available on a mirror.

Maybe somebody could compile a new package for that version. It's located here: https://aur.archlinux.org/cgit/aur.git/commit/?h=spotify&id=b49520c1f96a1c5e9079397686e2d315864c9a0e

The outdated deb is still located here: http://ucmirror.canterbury.ac.nz/linux/mint/packages/pool/import/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb

For now I'm just manually installing from the deb, and write-protecting it so hopefully it won't auto-update.

If somebody could make a new package for me, I would be forever indebted to you.

@kjozsa But this would break spotify on normal installs. If you have an idea on how dynamically solve it, I am happy to add that.

@all: Keyboard Media Keys do not work for me with the recent update. Do you also have this issue?

@CaninoDev Yes, it's been discussed previously. If you use yay, simply rerun yay -Syu over and over until it completes. This works because curl auto-resumes where it left off. Alternatives were also posted.

Is anyone else getting download issues for the .deb file? It would start to download, but around the ~23mb mark it would error out with a Network Error no matter how many attempts have been made.

I'm running spotify on a 4k screen using GNOME 40. I keep have to use the command spotify --force-device-scale-factor=2 to get Spotify realise the proper scaling, otherwise it runs unscaled. Can we get a workaround to this into the desktop file to make this work out of the box?

Getting checksum mismatches

==> Starting prepare()...
spotify-1.1.55.498-x86_64-Packages: OK
spotify-1.1.55.498-x86_64.deb: FAILED
sha512sum: WARNING: 1 computed checksum did NOT match
==> ERROR: A failure occurred in prepare().

But the hash seems correct

395806fc064706cc6b005054ec0f5e0a9b0cebfa073ccb771b7e8cb2f6c8aa300efe9164e492f90f4c83d047a898f6553c44722562d8f3e1462947d811a2e599  spotify-1.1.55.498-x86_64.deb

Update: Fixed - thank you!

@marcosfrm I'm using KDE Plasma and do not have this issue. Further, I don't see any files in /dev/shm when Spotify is running.

I am on XFCE and spotify 1.1.55.498 only works on the first run. If I close it, it always crashes on subsequent runs. It appears to leave stray files on /dev/shm. Already tried --no-zygote flag but it did not make difference.

I just tested it and I'm able to play video without lib32-atk.

Can someone else please test? I already have that 32bit lib installed, so I cannot test if it would not work without.

@NicoHood simplest way to test is to play an episode of Joe Rogan's podcast, which are all video episodes: https://open.spotify.com/episode/3RprQq9tdNbtNUl04vJvJf?si=wc5mMwt2Tfup5EDPSQCxsw Until I installed lib32-atk it would always say "Unable to play video".

@Link512 Why the 32bit version? atk is a required dependency, I am confused why the 32bit version would be needed. Is there a way to test video playback?

Can you please add lib32-atk as an optional dependency? It is needed in order to play videos.

Following on @polyzen's instructions, you need to rename the downloaded file to spotify-1.1.55.498-x86_64.deb and then rerun yay (or whatever)

Since the new version relies on GTK3 instead of GTK2, does it mean that there is support for wayland? Testing it under sway seems to still want to start the app with xwayland. Forcing GDK_BACKEND=wayland didn't solve it.

Another option to complete the failed download:

cd <path of your $SRCDEST>
wget --continue http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.55.498.gf9a83c60_amd64.deb

wget will keep retrying when it loses connection and --continue will continue off of what's already been downloaded.

@linuxmobile Keep trying and it will eventually complete. For example, if you use yay, keep issuing yay -Syu and, since it uses curl, it will resume where it left off.

For many of us, 5 or 6 times seems to do the trick.

I almost fell of my chair. Just installed spotify, and saw in advanced options "close to tray". My heart started beating really fast, no way they brought tray support on linux!!! Then i quickly realized the option is there, but doesn't work :( sad

From Latest update.

curl: (18) transfer closed with 124340401 bytes remaining to read ==> ERROR: Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.55.498.gf9a83c60_amd64.deb Aborting... error downloading sources: spotify

Great to see Spotify now using Gtk3.

@TaZeR Interesting idea. I simply rerun yay -Syu and curl will eventually download it, as it can resume where it left off.

My fix to the current problem (the error where it can't download the source file) is to download it manually, using aria2c (aria2c http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.55.498.gf9a83c60_amd64.deb)

Rename file to 'spotify-1.1.55.498-x86_64.deb' move to a build directory, modify the line 29 of PKGBUILD to: "${pkgname}-${pkgver}-x86_64.deb::${pkgver}.${_commit}_amd64.deb", then run makepkg.

@mgranat They didn't reject my ticket. They sent it on to their specialty team.

Using --retry-all-errors is not a workaround. It disables the ability for curl to continue at its last offset and retries from the beginning, among other nasty things. Since you cannot download the entire package, you'll end up in a never-ending loop.

Thanks for the link to their community page. I had not seen that. Now that I have a ticket number, I'm going to wait and see what happens. There's a thread on the community board from Feb that one person has replied to, but nothing from Spotify.

@lucidcomplex I am able to copy song links.

Is is just me, or copying song links from the app stopped working?

@tobfromme that page also states that this package is not officially supported and is maintained by devs in their spare time. Support is probably right to reject your ticket. It seems like everyone here has figured out how to work around this. One option is to add --retry-all-errors to your http download agent in makepkg.conf. The right support forum is probably the one linked on that same page.

I encourage everyone to log a support case at:

https://support.spotify.com/us/contact-spotify-support/

State that a download of:

http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.55.498.gf9a83c60_amd64.deb

fails midstream on all operating systems. I've tested multiple operating systems at different geographic locations and they all fail.

They attempted to tell me that's not their site, but their Linux page at:

https://www.spotify.com/us/download/linux/

specifically mentions the repository URL at the bottom.

I had the server problems as well, and it succeeded after 10 tries.

Thanks, everyone. It's good to know my sanity hasn't left the building (yet). Since it's an issue with repository.spotify.com, is there a way to update the PKGBUILD so the download is retried several times before giving up?

Same sever reset problem, solved after 5 attempts.

@D3SOX, Yeah, in my case, it was just gnome keyring locked after i changed my user password. Created a new keyring and its ok now.

@D3SOX its working fine, but it keeps asking my session password when i close. I believe its a problem with gnome keyring.

@pdimh So you have the same error as me. I thought it was just me. Can you play songs longer than 5-6 seconds? That doesn't work for me either.

Spotify keeps asking for password when i close the app. Is that expected?

I am having a similar issue with the constant resets from the server after a few megabytes of every attempt. And similarly it worked after around five tries

Anyone else getting constant resets from the server while downloading the package? After 5 or 6 attempts, it finally succeeds but it is annoying. This only happens with this package.

I've updated the PKGBUILD. It turns out that spotify finally switched to gtk3! :-)

There are a few more namcap errors and I am not sure, if some of these missing dependencies are required. If anyone got ideas on how to fix some of the errors, please let me know:

Checking PKGBUILD
PKGBUILD (spotify) W: Reference to x86_64 should be changed to $CARCH
PKGBUILD (spotify) W: Reference to x86_64 should be changed to $CARCH
PKGBUILD (spotify) W: Reference to x86_64 should be changed to $CARCH
PKGBUILD (spotify) W: Reference to x86_64 should be changed to $CARCH
PKGBUILD (spotify) W: Reference to x86_64 should be changed to $CARCH
PKGBUILD (spotify) W: Reference to x86_64 should be changed to $CARCH
Checking spotify-1:1.1.55.498-2-x86_64.pkg.tar.zst
spotify E: ELF files outside of a valid path ('opt/').
spotify W: ELF file ('opt/spotify/spotify') lacks FULL RELRO, check LDFLAGS.
spotify W: ELF file ('opt/spotify/spotify') lacks PIE.
spotify W: unneeded dependency on a package run when needed by hooks.
spotify W: Referenced library 'libcurl-gnutls.so.4' is an uninstalled dependency
spotify W: Referenced library 'libcef.so' is an uninstalled dependency
spotify W: Unused shared library '/usr/lib/librt.so.1' by file ('opt/spotify/libGLESv2.so')
spotify W: Unused shared library '/usr/lib/librt.so.1' by file ('opt/spotify/libcef.so')
spotify W: Unused shared library '/usr/lib/librt.so.1' by file ('opt/spotify/spotify')
spotify W: Unused shared library '/usr/lib/libSM.so.6' by file ('opt/spotify/spotify')
spotify W: Unused shared library '/usr/lib/libICE.so.6' by file ('opt/spotify/spotify')
spotify W: Unused shared library '/usr/lib/libXext.so.6' by file ('opt/spotify/spotify')
spotify W: Unused shared library '/usr/lib/libgdk-3.so.0' by file ('opt/spotify/spotify')
spotify W: Unused shared library '/usr/lib/libatk-1.0.so.0' by file ('opt/spotify/spotify')
spotify W: Unused shared library '/usr/lib/libpangocairo-1.0.so.0' by file ('opt/spotify/spotify')
spotify W: Unused shared library '/usr/lib/libcairo-gobject.so.2' by file ('opt/spotify/spotify')
spotify W: Unused shared library '/usr/lib/libpango-1.0.so.0' by file ('opt/spotify/spotify')
spotify W: Unused shared library '/usr/lib/libcairo.so.2' by file ('opt/spotify/spotify')
spotify W: Dependency alsa-lib included but already satisfied
spotify W: Dependency libsystemd included but already satisfied
spotify W: Dependency included and not needed ('libxss')
spotify W: Dependency desktop-file-utils included but already satisfied
spotify W: Dependency openssl included but already satisfied
spotify W: Dependency at-spi2-atk included but already satisfied
spotify W: Dependency included and not needed ('libcurl-gnutls')
spotify W: Dependency libice included but already satisfied

1.1.55.498.gf9a83c60 has been released.

Also, Release and Release.sig have been changed and this makes line 57 of current PKGBUILD fail (for older version of binary 1.1.55.494).

This is problematic as the prepare function doubles makepkg's signature and checksum process but doesn't honor the --skipgpgcheck or --skipchecksums flags of makepkg. As a result, the current package just doesn't build whatever the options. You have to edit the PKGBUILD.

IMHO the PKGBUILD should honor the makepkg flags one way or another.

This is a proposed cleaned-up PKGBUILD, removing leftovers from i686 support and refactoring the GPG check a bit.

# Maintainer: Ashley Whetter <(firstname) @ awhetter.co.uk>
# Co-Maintainer: NicoHood <archlinux {cat} nicohood {dog} de>
# PGP ID: 97312D5EB9D7AE7D0BD4307351DAE9B7C1AE9161
# Contributor: Eothred <yngve.levinsen@gmail.com>

pkgname=spotify
pkgver=1.1.55.498
epoch=1
_commit=gf9a83c60
pkgrel=1
pkgdesc='A proprietary music streaming service'
arch=('x86_64')
license=('custom')
url='https://www.spotify.com'
depends=('alsa-lib>=1.0.14' 'gtk2' 'libsystemd' 'libxss' 'desktop-file-utils' 'openssl' 'nss' 'at-spi2-atk')
depends_x86_64=('libcurl-gnutls')
optdepends=('ffmpeg-compat-57: Adds support for playback of local files'
            'zenity: Adds support for importing local files'
            'libnotify: Desktop notifications')
options=('!strip')

# NOTE: We switched from stable to testing on 18th march, as the spotify
# stable repository is always outdated. Testing seems to be in sync with snap:
# https://snapcraft.io/spotify
# http://repository.spotify.com/dists/testing/Release
# http://repository.spotify.com/dists/testing/non-free/binary-amd64/Packages
# http://repository.spotify.com/dists/testing/Release.gpg
source=('spotify.protocol'
        'LICENSE'
        "${pkgname}-${pkgver}-x86_64.deb::http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_${pkgver}.${_commit}_amd64.deb"
        # For signature checking
        "${pkgname}-${pkgver}-x86_64-Packages::http://repository.spotify.com/dists/testing/non-free/binary-amd64/Packages"
        "${pkgname}-${pkgver}-Release::http://repository.spotify.com/dists/testing/Release"
        "${pkgname}-${pkgver}-Release.sig::http://repository.spotify.com/dists/testing/Release.gpg")
sha512sums=('999abe46766a4101e27477f5c9f69394a4bb5c097e2e048ec2c6cb93dfa1743eb436bde3768af6ba1b90eaac78ea8589d82e621f9cbe7d9ab3f41acee6e8ca20'
            '2e16f7c7b09e9ecefaa11ab38eb7a792c62ae6f33d95ab1ff46d68995316324d8c5287b0d9ce142d1cf15158e61f594e930260abb8155467af8bc25779960615'
            '395806fc064706cc6b005054ec0f5e0a9b0cebfa073ccb771b7e8cb2f6c8aa300efe9164e492f90f4c83d047a898f6553c44722562d8f3e1462947d811a2e599'
            # For signature checking
            'SKIP'
            'SKIP'
            'SKIP')
validpgpkeys=('8FD3D9A8D3800305A9FFF259D1742AD60D811D58') # Spotify <tux@spotify.com>
# Old Keys:
# 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90
# 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45

prepare() {
    local sha_Packages sha_deb
    if (( ! SKIPPGPCHECK )); then
        # Validate hashes from the PGP signed "Release" file
        # Validate sha256 of "Packages" from "Release"
        sha_Packages="$(awk 'inshablock&&/non-free\/binary-amd64\/Packages$/{print $1} /SHA256/{inshablock=1} /(SHA|MD5)/&&!/SHA256/{inshablock=0}' ${pkgname}-${pkgver}-Release)"
        verify_integrity_one "${pkgname}-${pkgver}-x86_64-Packages" "sha256" "$sha_Packages"
        # Validate sha512 of binary from "Packages"
        sha_deb="$(awk '/Package:/{if($2 ~ /spotify-client/){inpkg=1}else{inpkg=0}} inpkg&&/SHA512:/{print $2}' ${pkgname}-${pkgver}-x86_64-Packages)"
        verify_integrity_one "${pkgname}-${pkgver}-x86_64.deb" "sha512" "$sha_deb"
    fi
}

package() {
    cd "${srcdir}"

    tar -xzf data.tar.gz -C "${pkgdir}"

    install -Dm644 "${pkgdir}"/usr/share/spotify/spotify.desktop "${pkgdir}"/usr/share/applications/spotify.desktop
    install -Dm644 "${pkgdir}"/usr/share/spotify/icons/spotify-linux-512.png "${pkgdir}"/usr/share/pixmaps/spotify-client.png

    for size in 22 24 32 48 64 128 256 512; do
        install -Dm644 "${pkgdir}/usr/share/spotify/icons/spotify-linux-$size.png" \
            "${pkgdir}/usr/share/icons/hicolor/${size}x${size}/apps/spotify.png"
    done

    # Move spotify binary to its proper location
    mkdir -p "${pkgdir}"/opt/spotify
    mv "${pkgdir}/usr/share/spotify" "${pkgdir}/opt/"

    # Symlink spotify binary which is located in /opt
    ln -sf /opt/spotify/spotify "${pkgdir}/usr/bin/spotify"

    # Copy protocol file for KDE
    install -Dm644 "${srcdir}/spotify.protocol" "${pkgdir}/usr/share/kservices5/spotify.protocol"

    # Install license
    # https://www.spotify.com/legal/end-user-agreement
    install -Dm 644 LICENSE "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"

    # Fix permissions
    chmod -R go-w "${pkgdir}"
}

@chovy

The file is listed here: http://repository.spotify.com/pool/non-free/s/spotify-client/

I can confirm upon clicking the current file there is a 404 error. My guess is that this is due to them recently updating the testing repo. It appeared they had pushed 1.1.55.494 to the stable Debian repos, but they have now replaced that with 1.1.55.498.

You could replace the link, but you would also need to replace the sha512sum.

For now, it is just broken until the PKGBUILD maintainer fixes it. You could alternatively use spotify-snap in the mean time.

  -> Downloading spotify-1.1.55.494-x86_64.deb...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0   162    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404
==> ERROR: Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.55.494.gca75f788_amd64.deb
    Aborting...
error downloading sources: spotify

404

We will see what happens, but spotify released 1.1.55.498 to the snapcraft stable channel about 10 hours ago. It seems to be a pretty incremental update, but it may still help us gauge how spotify will continue with the Debian repository.

As of this moment, the 1.1.55.498 update has yet to be released in even the testing repo http://repository.spotify.com/dists/testing/non-free/binary-amd64/Packages

Perhaps this shows that spotify is not going to release incremental updates to the Debian repository, or it could show that the release a few days ago was a one-off event. Unfortunately there are no clear answers from the Spotify team. Regardless, it is clear regular Debian packages are not their priority.

edit: they have now updated the testing repo. Here is the link for the latest package: http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.55.498.gf9a83c60_amd64.deb

There was a (now deleted) recent comment about Local Files working or not. For me, for the first time ever, they ARE working. spotify 1:1.1.55.494-1, ffmpeg-compat-57 3.4.2-3, zenity 3.32.0+55+gd7bedff-1

Same problem with the new version. I have to re-login every time I open it and it just plays 5 seconds and stops... (Although local file playback works)

The app works fine without gtk2 installed. Any thoughts why it should be in the deps?

@lenhuppe 's comment helped, spotify needs to sort their shit out

@dno I had the same problem!

Using @lenhuppe's advice below I too was able to make this work by downloading the .deb file. I want to add that I used wget which failed and retried 10(!) times and ultimately succeeded. Because that bad boy is relentless.

I have an easy workaround. Download the spotify client debian package from https://repository-origin.spotify.com/pool/non-free/s/spotify-client/ and then copy it to your build directory. Next edit PKGBUILD and change the "source_x86_64=" line from the url to the file path. From there it's "makepkg -sic" as usual.

 source_x86_64=("${pkgname}-${pkgver}-x86_64.deb::file:///path_to_build_directory/spotify-client_1.1.55.494.gca75f788_amd64.deb"

I can't update the package nor install it again. This is what shows up:

==> Validating source files with sha512sums...
    spotify.protocol ... Passed
    LICENSE ... Passed
    spotify-1.1.55.494-Release ... Skipped
    spotify-1.1.55.494-Release.sig ... Skipped
==> Validating source_x86_64 files with sha512sums...
    spotify-1.1.55.494-x86_64.deb ... FAILED
    spotify-1.1.55.494-x86_64-Packages ... Passed
==> ERROR: One or more files did not pass the validity check!
Failed to build spotify

I had to manually download the deb file with wget into ~/.cache/paru/clone/spotify.

@olorin364 their server is probably being hammered right now with people trying to update other clients

Thank you for the new version!

@omgronny Thanks for the tip about the download failure problem. I downloaded it successfully with wget, slapped it into my paru cache directory, and it worked great. Seems strange to me that their server would keep killing the download as it's currently doing, but I don't know enough about web server administration to judge it.

@CReimer

I similarly made a project that could now be redundant. https://github.com/ThePoorPilot/Unofficial-Spotify

I applied the same sort of Snap-based approach, but to building Debian packages(just for fun, I would never use such a distro)

It still remains to be seen if Spotify will again start making consistent releases of their stable packages in .deb format.

@LiterallyJohnny @driventub

For those who encountered the downloading problem:

ERROR: Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb
    Aborting...
error downloading sources: spotify

The workaround would be downloading directly through your browser, then copy the deb package to ~/.cache/yay/spotify (I use yay), rename it to the correct name. You can check PKGBUILD for correct file name or look for the interrupted downloading *.part file. Eventually, rerun update and DON'T DO cleanBuild, which will delete files you downloaded.

@lordchaos thanks! The hard part is actually always unflagging the package out of date XD

@CReimer sure. You could notify your users about the update and open a deletion request in a few weeks. Just let me know, so I can accept it for you. If the package gets out of date you can reactivate your snap package, just keep a local backup or checkout the aur git (which is not lost on deletion I think).

New version seems to work fine; I just upgraded. Thank you for all the hard work.

I'm not sure what I'm going to do with spotify-snap and spotify-edge-snap now. I think I'll keep them updated for the forseeable future. In case Spotify decides to stop updating the Debian repository again, we have some kind of fallback.

@bryanOmalley thanks for the note! If the version matches the snap I see no reason on why to hold back updates and be older than ubuntu. I've switches to the testing repo.

After the first start, playing a playlist I had a segmentation fault (crash). After the next start it all worked fine. Please report any issues.

@bryanOmalley That does seem to be a viable solution.

It would just be a matter of if the maintainer of this pkgbuild wants to switch.

While the updated packages are in the "testing" repository, they are also the same versions classified as stable by Spotify on their snap page.

Please tell me that I could be onto something here. Just today, there was an update at the testing branch: http://repository.spotify.com/dists/testing/non-free/binary-amd64/Packages Maybe this was already regularly updated, I don't know, but let's hope for the best!

@e3a4:

I am having the exact same issue, youre not alone.

Does anyone else have issues with closing the window? It closes after a two seconds delay when I kill the window. I'm using GNOME.

@ThePoorPilot:

https://github.com/flathub/com.spotify.Client/commit/8890b82d5e82f90e97ee1e8e38c19f88b5e57e48

Unfortunately the exact same problem...

@NicoHood

I don't know if the flatpak package would satisfy your requirements for verification, but it does looks like there is way to do it. I did a little experimentation and made a post about it here: https://forum.garudalinux.org/t/unofficial-up-to-date-spotify-package-that-could-be-installed-with-pacman-based-upon-flatpak/5424/

I have a massive problem. I always have to re-login on every start of the program and it no longer plays back correctly. It just plays 3-6 seconds, stops playing and says "Can't play the current song" I'm experiencing this problem since about 1 week now...

@dark_barker This AUR package packages the dpkg Spotify has released, which is rather out of date. If you install spotify-snap instead, it packages the snapcraft version, which Spotify has updated more recently and should work for you.

login via facebook is still not possible (on 1.1.42)... this is a problem requiring some solutions imho

@LiterallyJohnny I have the same problem @NicoHood Is there a way to install with the repository that you pinned in a comment?, or simply it won't work until the further notice?

@markoff I think everyone gets libcurl-gnutls.so.4 errors...

Is there any way to fix this ? Ive checked a few answers in the forums and Im not able to install the deb packages (using debtap) in the first place

https://community.spotify.com/t5/Desktop-Linux/Segmentation-fault-core-dumped-is-back/m-p/4813658/highlight/true#M18972

I can't use local files with this

I think we're missing a dependency. I get a segfault when I hit my username and hit the change picture circle.

Problem persists in the spotify-snap package.

In the spotify snap, a file chooser pops up, but the font is all rectangles.

@NicoHood: Thanks. I hope so, too. I went ahead and created spotify-snap. Still not particularly happy about repackaging a snap. I will orphan it once there is a better solution

I've pinned the spotify post by Creimer. Please upvote this post, so spotify will see it. With our last post we made 3k likes until spotify noticed the post and closed it (the introduced snap after that). Now we need to get spotify in updating the package more frequently or providing us with some software tarballs that are signed properly.

@CReimer: If you want to maintain a spotify-snap package that'd be cool for me. Thats a lot for your Post on the spotify forum. I hope they will respond.

Anybody else unable to install Spotify with the yay AUR helper? I keep getting this error below:

ERROR: Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb
    Aborting...
error downloading sources: spotify

@markoff I think everyone gets libcurl-gnutls.so.4 errors...

FWIW, the podcast doesn't work for me either.

@Pryka, thanks for replying. That is weird, it doesn't on mine. I am getting the following message though, could be due to this:

/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)

Could it be due to that?

@markoff

They are working fine on my machine(They even have video feed!)

looks like they won't be releasing debian packages. This package is very old now. Lets just use snap as a source.

Can anyone test Joe Rogan's podcast (on spotify) and let me know if it works? After I click to listen, nothing happens. It seems to be on "loading", but never loads.

Facebook logging not working.

Why is this still flagged out-of-date?

Is possible to not opening the new spotify instance - window while clicking new spotify hyperlinks?

FIY: I decided to ask Spotify directly. I usually don't push for GPG signatures (at least not as much as NicoHood does :-D), but having to trust Canonical just doesn't feel right

https://community.spotify.com/t5/Desktop-Linux/Debian-repository-is-out-of-date/td-p/5152530

Flathub also switched over to snap as source. I had hoped to find an official source from spotify.com somewhere. But no luck so far.

https://github.com/flathub/com.spotify.Client/commit/8890b82d5e82f90e97ee1e8e38c19f88b5e57e48

@NicoHood -- for what it's worth, I'm also happy to co-maintain the package if you'd like extra help.

As far as I can tell, the way the snap store works is:

• Fetch https://api.snapcraft.io/v2/snaps/info/spotify (with the Snap-Device-Series header set to 16, the only valid value). This returns a JSON object over TLS describing where to download it, as well as SHA3-384 hashes:

  {
    "channel-map": [
      {
        "channel": {
          "architecture": "amd64",
          "name": "stable",
          "released-at": "2020-11-16T12:00:15.215296+00:00",
          "risk": "stable",
          "track": "latest"
        },
        "created-at": "2020-11-16T11:40:36.759819+00:00",
        "download": {
          "deltas": [],
          "sha3-384": "aa2181403902b64a3014071385bb20cbade080a458c6dbefdd1787d3a6136f1b0d8ac3aece4f94f1596fdea0bc5deae6",
          "size": 181366784,
          "url": "https://api.snapcraft.io/api/v1/snaps/download/pOBIoZ2LrCB3rDohMxoYGnbN14EHOgD7_43.snap"
        },
        "revision": 43,
        "type": "app",
        "version": "1.1.46.916.g416cacf1"
      },
      {
        "channel": {
          "architecture": "amd64",
          "name": "candidate",
          "released-at": "2020-11-16T12:00:15.215296+00:00",
          "risk": "candidate",
          "track": "latest"
        },
        "created-at": "2020-11-16T11:40:36.759819+00:00",
        "download": {
          "deltas": [],
          "sha3-384": "aa2181403902b64a3014071385bb20cbade080a458c6dbefdd1787d3a6136f1b0d8ac3aece4f94f1596fdea0bc5deae6",
          "size": 181366784,
          "url": "https://api.snapcraft.io/api/v1/snaps/download/pOBIoZ2LrCB3rDohMxoYGnbN14EHOgD7_43.snap"
        },
        "revision": 43,
        "type": "app",
        "version": "1.1.46.916.g416cacf1"
      },
      {
        "channel": {
          "architecture": "amd64",
          "name": "edge",
          "released-at": "2021-02-09T15:18:59.323147+00:00",
          "risk": "edge",
          "track": "latest"
        },
        "created-at": "2021-02-09T15:16:39.756041+00:00",
        "download": {
          "deltas": [],
          "sha3-384": "f097a1de1763a9598e8e9bee0c6560f73f9893af2efd518b07aca20cd76ef3343eda71ee42d586213c292dd8c9a60ace",
          "size": 183443456,
          "url": "https://api.snapcraft.io/api/v1/snaps/download/pOBIoZ2LrCB3rDohMxoYGnbN14EHOgD7_44.snap"
        },
        "revision": 44,
        "type": "app",
        "version": "1.1.52.687.gf5565fe5"
      }
    ],
    "default-track": null,
    "name": "spotify",
    "snap": {
      "license": "Proprietary",
      "name": "spotify",
      "prices": {},
      "publisher": {
        "display-name": "Spotify",
        "id": "Z7emHVerQzTDQrOcaLJ8wO1ir1NPl3fG",
        "username": "spotify",
        "validation": "verified"
      },
      "snap-id": "pOBIoZ2LrCB3rDohMxoYGnbN14EHOgD7",
      "store-url": "https://snapcraft.io/spotify",
      "summary": "Music for everyone",
      "title": "Spotify"
    },
    "snap-id": "pOBIoZ2LrCB3rDohMxoYGnbN14EHOgD7"
  }
  

• Fetch the package at the URL listed in the above JSON. This downloads a squashfs image, which should match the sha3-384 hash in the above JSON. The URL is documented as being GET /api/v1/snaps/download/<filename>, but I've noticed that <filename> always seesm to be {snap_id}_{revision}.snap, so my PKGBUILD uses that. This url redirects to download from a canonical-operated CDN (over TLS).

• Optionally, download "assertions" and decide if you accept them. Assertions are various bits of metadata about the software (publisher name, expected permissions) and are all digitally signed ... by Canonical. I'm not sure if it's possible for assertions to be signed by the package vendor (Spotify), but at least for the spotify package none of them are. This seems to be much less of "this is really the right spotify package -- look, we signed stuff" and more of "spotify wants to talk to pulseaudio; is that okay." As far as I can tell, packages might be signed by their vendors when uploaded, but snapcraft doesn't expose any way to fetch and validate that signature; it's assumed that if you're using it you trust canonical.

In my PKGBUILD, I've skipped the first step and put the snap-id and stable revision in the PKGBUILD. Also, since makepkg doesn't support sha3-384, I downloaded the snap, verified the sha3-384 hash, and calculated its sha512 hash to put in the PKGBUILD. It might be worth creating a script to automate this process for updating, but it's relatively simple to do.

Once we download the squashfs image, snap wants you to run it in some sort of container, but I just extract the /usr/share/spotify directory from it, and do with that exactly what we used to do with the /usr/share/spotify directory from the dpkg.

Unfortunately, snaps are not signed. The closest they have is there are "assertions" which contain various bits of information including the hash of the package and are signed, but they are all signed by canonical instead of the package vendor and so are IMO pretty worthless. (If you already trust canonical, then the whole store is over TLS so you don't need them. If not, then what's the point)

That is a good idea, I will see what I can do. I would like to have GPG signatures for the package, I need to check how to get them. Hopefully the snap store is not another security broken store/dependency resolver.

@NicoHood can you please update the package or let @CReimer or someone else willing to maintain it do that?

@gavinsyancey: Already provided a PKGBUILD for the snap. See my comment from 2021-01-24

@all: I want to add, that I'd be happy to take over or co-maintain the spotify package in AUR. If that opportunity may arise. I use spotify daily and therefore need it to be up-to-date myself

Since it looks like they're not updating the deb package but are updating their snap package, I updated the PKGBUILD to fetch and extract spotify from the snap package. Are you interested in pulling in my changes, or should I make a separate package for pulling from the snap?

Note -- My change is not "install the snap," but "download the snap, extract relevant files, put them where they're supposed to go." I've tested it and it seems to work just as well as (and just about the same as) the old deb-based package.

My patch:

From 33119ccc046daadee1f0c6dce9ba03de32b7989c Mon Sep 17 00:00:00 2001
From: Gavin Yancey <gyancey@hmc.edu>
Date: Thu, 11 Feb 2021 23:32:55 -0800
Subject: [PATCH] Switch to pulling from snap, because it's more up-to-date.

---
 .SRCINFO | 18 +++++---------
 PKGBUILD | 71 ++++++++++++++++++--------------------------------------
 2 files changed, 28 insertions(+), 61 deletions(-)

diff --git a/.SRCINFO b/.SRCINFO
index 1cc90cc..7ea35da 100644
--- a/.SRCINFO
+++ b/.SRCINFO
@@ -1,11 +1,12 @@
 pkgbase = spotify
    pkgdesc = A proprietary music streaming service
-   pkgver = 1.1.42.622
-   pkgrel = 2
+   pkgver = 1.1.46.916.g416cacf1
+   pkgrel = 1
    epoch = 1
    url = https://www.spotify.com
    arch = x86_64
    license = custom
+   makedepends = squashfs-tools
    depends = alsa-lib>=1.0.14
    depends = gtk2
    depends = libsystemd
@@ -14,24 +15,17 @@ pkgbase = spotify
    depends = openssl
    depends = nss
    depends = at-spi2-atk
+   depends = libcurl-gnutls
    optdepends = ffmpeg-compat-57: Adds support for playback of local files
    optdepends = zenity: Adds support for importing local files
    optdepends = libnotify: Desktop notifications
    options = !strip
    source = spotify.protocol
    source = LICENSE
-   source = spotify-1.1.42.622-Release::http://repository.spotify.com/dists/stable/Release
-   source = spotify-1.1.42.622-Release.sig::http://repository.spotify.com/dists/stable/Release.gpg
-   validpgpkeys = 8FD3D9A8D3800305A9FFF259D1742AD60D811D58
+   source = spotify-1.1.46.916.g416cacf1.snap::https://api.snapcraft.io/api/v1/snaps/download/pOBIoZ2LrCB3rDohMxoYGnbN14EHOgD7_43.snap
    sha512sums = 999abe46766a4101e27477f5c9f69394a4bb5c097e2e048ec2c6cb93dfa1743eb436bde3768af6ba1b90eaac78ea8589d82e621f9cbe7d9ab3f41acee6e8ca20
    sha512sums = 2e16f7c7b09e9ecefaa11ab38eb7a792c62ae6f33d95ab1ff46d68995316324d8c5287b0d9ce142d1cf15158e61f594e930260abb8155467af8bc25779960615
-   sha512sums = SKIP
-   sha512sums = SKIP
-   source_x86_64 = spotify-1.1.42.622-x86_64.deb::http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb
-   source_x86_64 = spotify-1.1.42.622-x86_64-Packages::http://repository.spotify.com/dists/stable/non-free/binary-amd64/Packages
-   depends_x86_64 = libcurl-gnutls
-   sha512sums_x86_64 = a3fe98d69460ffd641df3219c2a3d164a33e2b52c86a56276e473dd5c3a43d6304df3b77fefcf0ca6c09cb6e2c8dacab65573cf7543725b6c8d402832149e122
-   sha512sums_x86_64 = af7eb8c50e003638cab04ef1cad36f43379e678a1071c65844a6ff8963434b427044b76159e51c1383698c309c814261ed85aab02ffb86ac73ee86181aada5e9
+   sha512sums = 5b3d5d1f52a554c8e775b8aed16ef84e96bf3b61a2b53266e10d3c47e341899310af13cc8513b04424fc14532e36543a6fae677f80a036e3f51c75166d8d53d1

 pkgname = spotify

diff --git a/PKGBUILD b/PKGBUILD
index 75c3454..fffa669 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -2,85 +2,58 @@
 # Co-Maintainer: NicoHood <archlinux {cat} nicohood {dog} de>
 # PGP ID: 97312D5EB9D7AE7D0BD4307351DAE9B7C1AE9161
 # Contributor: Eothred <yngve.levinsen@gmail.com>
+# Contributor: Gavin Yancey <gyancey@hmc.edu>

 pkgname=spotify
-pkgver=1.1.42.622
+
 epoch=1
-_commit=gbd112320
-_ver_x86_64=37
-#_ver_i686=10
-pkgrel=2
+# Extracted from `curl -H 'Snap-Device-Series: 16' https://api.snapcraft.io/v2/snaps/info/spotify`
+_snap_id=pOBIoZ2LrCB3rDohMxoYGnbN14EHOgD7
+_revision=43
+pkgver=1.1.46.916.g416cacf1
+pkgrel=1
+
 pkgdesc='A proprietary music streaming service'
 arch=('x86_64')
 license=('custom')
 url='https://www.spotify.com'
-depends=('alsa-lib>=1.0.14' 'gtk2' 'libsystemd' 'libxss' 'desktop-file-utils' 'openssl' 'nss' 'at-spi2-atk')
-depends_x86_64=('libcurl-gnutls')
-depends_i686=('libcurl-compat')
+depends=('alsa-lib>=1.0.14' 'gtk2' 'libsystemd' 'libxss' 'desktop-file-utils' 'openssl' 'nss' 'at-spi2-atk' 'libcurl-gnutls')
 optdepends=('ffmpeg-compat-57: Adds support for playback of local files'
             'zenity: Adds support for importing local files'
             'libnotify: Desktop notifications')
+makedepends=('squashfs-tools')
 options=('!strip')

-# http://repository.spotify.com/dists/stable/Release
-# http://repository.spotify.com/dists/stable/non-free/binary-amd64/Packages
-# http://repository.spotify.com/dists/stable/non-free/binary-i386/Packages
-# http://repository.spotify.com/dists/stable/Release.gpg
+# URL schema extracted from `curl -H 'Snap-Device-Series: 16' https://api.snapcraft.io/v2/snaps/info/spotify`
+# See https://api.snapcraft.io/docs/info.html for more info
 source=('spotify.protocol'
         'LICENSE'
-        "${pkgname}-${pkgver}-Release::http://repository.spotify.com/dists/stable/Release"
-        "${pkgname}-${pkgver}-Release.sig::http://repository.spotify.com/dists/stable/Release.gpg")
-source_x86_64=("${pkgname}-${pkgver}-x86_64.deb::http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_${pkgver}.${_commit}-${_ver_x86_64}_amd64.deb"
-               "${pkgname}-${pkgver}-x86_64-Packages::http://repository.spotify.com/dists/stable/non-free/binary-amd64/Packages")
-# source_i686=("${pkgname}-${pkgver}-i686.deb::http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_${pkgver}.${_commit}-${_ver_i686}_i386.deb"
-#              "${pkgname}-${pkgver}-i686-Packages::http://repository.spotify.com/dists/stable/non-free/binary-i386/Packages")
+        "${pkgname}-${pkgver}.snap::https://api.snapcraft.io/api/v1/snaps/download/${_snap_id}_${_revision}.snap")
 sha512sums=('999abe46766a4101e27477f5c9f69394a4bb5c097e2e048ec2c6cb93dfa1743eb436bde3768af6ba1b90eaac78ea8589d82e621f9cbe7d9ab3f41acee6e8ca20'
             '2e16f7c7b09e9ecefaa11ab38eb7a792c62ae6f33d95ab1ff46d68995316324d8c5287b0d9ce142d1cf15158e61f594e930260abb8155467af8bc25779960615'
-            'SKIP'
-            'SKIP')
-sha512sums_x86_64=('a3fe98d69460ffd641df3219c2a3d164a33e2b52c86a56276e473dd5c3a43d6304df3b77fefcf0ca6c09cb6e2c8dacab65573cf7543725b6c8d402832149e122'
-                   'af7eb8c50e003638cab04ef1cad36f43379e678a1071c65844a6ff8963434b427044b76159e51c1383698c309c814261ed85aab02ffb86ac73ee86181aada5e9')
-validpgpkeys=('8FD3D9A8D3800305A9FFF259D1742AD60D811D58') # Spotify <tux@spotify.com>
-# Old Keys:
-# 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90
-# 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45
-
-# Spotify uses different names for the arch
-if [ "${CARCH}" = "i686" ]; then
-    _SPOTIFY_ARCH=i386
-else
-    _SPOTIFY_ARCH=amd64
-fi
+            '5b3d5d1f52a554c8e775b8aed16ef84e96bf3b61a2b53266e10d3c47e341899310af13cc8513b04424fc14532e36543a6fae677f80a036e3f51c75166d8d53d1')

 prepare() {
-    # Validate hashes from the PGP signed "Release" file
-    echo "$(grep non-free/binary-${_SPOTIFY_ARCH}/Packages ${pkgname}-${pkgver}-Release | tail -n 2 | head -n 1 | awk '{print $1}') ${pkgname}-${pkgver}-${CARCH}-Packages" \
-        > "${pkgname}-${pkgver}-${CARCH}-Packages.sha256"
-    sha256sum -c "${pkgname}-${pkgver}-${CARCH}-Packages.sha256"
-
-    echo "$(grep SHA512 ${pkgname}-${pkgver}-${CARCH}-Packages | head -n 1 | awk '{print $2}') ${pkgname}-${pkgver}-${CARCH}.deb" \
-        > "${pkgname}-${pkgver}-${CARCH}.deb.sha512"
-    sha512sum -c "${pkgname}-${pkgver}-${CARCH}.deb.sha512"
+    # Extract the snap (it's a squashfs image)
+    rm -rf "${srcdir}/squashfs-root"
+    unsquashfs -d "${srcdir}/squashfs-root" "${srcdir}/${pkgname}-${pkgver}.snap" usr/share/spotify
 }

 package() {
-    cd "${srcdir}"
-
-    tar -xzf data.tar.gz -C "${pkgdir}"
-
-    install -Dm644 "${pkgdir}"/usr/share/spotify/spotify.desktop "${pkgdir}"/usr/share/applications/spotify.desktop
-    install -Dm644 "${pkgdir}"/usr/share/spotify/icons/spotify-linux-512.png "${pkgdir}"/usr/share/pixmaps/spotify-client.png
+    install -Dm644 "${srcdir}/squashfs-root"/usr/share/spotify/spotify.desktop "${pkgdir}"/usr/share/applications/spotify.desktop
+    install -Dm644 "${srcdir}/squashfs-root"/usr/share/spotify/icons/spotify-linux-512.png "${pkgdir}"/usr/share/pixmaps/spotify-client.png

     for size in 22 24 32 48 64 128 256 512; do
-        install -Dm644 "${pkgdir}/usr/share/spotify/icons/spotify-linux-$size.png" \
+        install -Dm644 "${srcdir}/squashfs-root/usr/share/spotify/icons/spotify-linux-$size.png" \
             "${pkgdir}/usr/share/icons/hicolor/${size}x${size}/apps/spotify.png"
     done

     # Move spotify binary to its proper location
     mkdir -p "${pkgdir}"/opt/spotify
-    mv "${pkgdir}/usr/share/spotify" "${pkgdir}/opt/"
+    cp -dpr --no-preserve=ownership "${srcdir}/squashfs-root/usr/share/spotify" "${pkgdir}/opt/"

     # Symlink spotify binary which is located in /opt
+    mkdir -p "${pkgdir}/usr/bin"
     ln -sf /opt/spotify/spotify "${pkgdir}/usr/bin/spotify"

     # Copy protocol file for KDE
--
2.30.1

I cant install spotify and i dont know why, a tried in paru, yay and git clone i always get this -> Downloading spotify-1.1.42.622-Release... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 2434 100 2434 0 0 6668 0 --:--:-- --:--:-- --:--:-- 6668 -> Downloading spotify-1.1.42.622-Release.sig... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 833 100 833 0 0 2814 0 --:--:-- --:--:-- --:--:-- 2814 -> Downloading spotify-1.1.42.622-x86_64.deb... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 53 120M 53 64.8M 0 0 4294k 0 0:00:28 0:00:15 0:00:13 4656k curl: (18) transfer closed with 58287280 bytes remaining to read ==> ERROR: Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb Aborting... :: Packages failed to build: spotify-1:1.1.42.622-2

pls help

Does it actually require gtk2?

With this version i cant log with facebook. It says the version is too old XDD

So I understand that we need to wait for an update of a stable version to be able to login with Facebook? Edit: I found a workaround. You can disconnect Spotify account from Facebook. Use "recover password" and then disconnect the app from Facebook (tick the checkbox to notify Spotify about it), then you can login with email associated with Facebook and newly created password.

Doing a cleanBuild fixed invalid public key 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45 issue for me (I'm using yay AUR helper):

:: 1 Packages to upgrade.                                                                                                                                                     
1  aur/spotify  1:1.1.42.622-1 -> 1:1.1.42.622-2                                                                                                                              
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)                                                                                                              
==>                                                                                                                                                                           
:: Checking for conflicts...                                                                                                                                                  
:: Checking for inner conflicts...                                                                                                                                            
[Aur:1]  spotify-1:1.1.42.622-2                                                                                                                                               

  1 spotify                          (Installed) (Build Files Exist)
==> Packages to cleanBuild?        
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> a

This is probably marked out-of-date because you can't login with facebook anymore if it hasn't been logged in before.

Interesting. So Spotify prefers the snapstore now?

Here's an updated PKGBUILD which repackages the snapstore version

https://github.com/CReimer/aur_spotify

Things missing:

• the snapstore uses sha3-384 for its checksums, which doesn't seem to be supported by makepkg

• I had to remove the gpg stuff from the PKGBUILD. Is there an equivalent in the snapstore or do they rely on the checksum only?

Edit: I also figured out that a bunch of stuff in the spotify package is unneeded. e.g libEGL and libGLES don't need to be bundled. It works fine with the default ones from Arch

Whoever has flagged this for out-of-date need to know that this repo relies entirely on spotify's Ubuntu/Debian repository which hasnt been updated yet, unlike the snap which features the requested version. I do see this isnt a valid reason to flag it out of date.

I'm curious. Why is this marked out-of-date again? Even though it is clearly still the latest release...

dav1d update conflicts with old version of ffmpeg that enables local files playback. Wonder how big ignore-pkg will grow until proper client update come out.

dav1d 0.7.1-1
x264 3:0.159.r2999.296494a-1
ffmpeg 2:4.2.3-2
ffmpeg-compat-57 3.4.2-3

works nicely for me.

I added the pubkey in the pinned comment but still get the unverified PGP signature error.

Spotify's repo is still flaky for me. Trizen uses curl which doesn't retry after failure, so as a workaround I used wget to download the .deb in the /tmp dir that trizen downloads to, then ran trizen again. Curl will see that the file has already been downloaded and trizen will continue.

@baalajimaestro I unflagged it now that it's working.

Spotify repos do seem to work now, request the maintainer to remove the flag :)

Can confirm that something is wrong with spotify's servers with the connection getting closed randomly in the middle of the download. However, retrying the download a few times with wget eventually worked for me.

I've flagged this as out of date for now, until it has a working mirror. The package doesn't work as is anyway.

Currently, the one it's using at http://repository.spotify.com/pool/non-free/s/spotify-client/ doesn't work.

This isn't the maintainers' fault, but rather Spotify's server.

The package isn't downloading for me even though I have a solid internet connection.

==> ERROR: Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb

Spotify stopped working for me unfortunately. It constantly shows as offline. When I try to relogin it says that either a firewall is blocking the connection or I need tzo adjust my proxy settings.

Does anybody know what I can do?

I dont use any firewall. Every other app works.

Spotify stopped working for me unfortunately. It constantly shows as offline. When I try to relogin it says that either a firewall is blocking the connection or I need tzo adjust my proxy settings.

Does anybody know what I can do?

I dont use any firewall. Every other app works.

As recently announced GTK2 has reached EOL now. Spotify still uses GTK2. I've opened a bug report at the spotify forum.

I kindly ask everyone to upvote the following post in order to still support spotify on Arch Linux in the future: https://community.spotify.com/t5/Desktop-Linux/Spotify-for-Linux-uses-GTK2-which-is-End-of-life-EOL-now/m-p/5096375/highlight/true#M20236

Why is this package marked out-of-date again? 1.1.42.622.gbd112320-37 is still the latest version. Even the testing version of spotify is 1.1.42.622.gbd112320-37

I'm also experiencing where opening the file browser crashes the entire application. Using cinnamon DE and fully updated

Used to have play/pause and skip keyboard shortcut control with spotify but now I dont for some reason. All other fn keys are working properly. Any ideas how to get it working again with Spotify?

Can confirm the issues opening a file browser for local files on I3 with a fully updated system

I cannot update because

==> Vérification des signatures des fichiers sources grâce à gpg…
    spotify-1.1.42.622-Release ... ÉCHEC (clé publique non valide 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45)
==> ERREUR : Une ou plusieurs signatures PGP n’ont pas pu être vérifiées.

Translation: ERROR : one or more PGP signatures could not be verified.

I tried to add the GPG key with the link provided by the pinned comment, but it does not work.

Spotify crashes everytime file selector opens like while selecting playlist cover or selecting local audio source on Gnome

Can anyone listen to Joe Rogan's podcast while using this version of spotify?

@D3SOX Yes I know optimal dependencies is a thing and has a purpose I just didn't see how this was one of those cases but given the fact that ffmpeg-compat-57 has to be built from source and that the spotify app can do everything except play local files without it I can see why it was marked optional. I wish the spotify company would compile it as part of the spotify bin but given the fact that the Mac version of Spotify doesn't display desktop notifications of the song playing I guess I shouldn't be surprised.

@LinuxLoverForeve see https://wiki.archlinux.org/index.php/PKGBUILD#optdepends The program works without those packages. Some folks might not even use this feature and therefore don't need to install them

@D3SOX My bad I didn't see it there but I'm also surprised it's considered optional because IMO the functionality it provides is part of the core app not an add-on. I even downloaded clementine a while back because I wanted to play my local files and didn't think it was possible to do on this install of spotify.

@LinuxLoverForeve It is clearly listed as optional dependency. Always check those when installing packages ^^

It should a pinned comment here that if you want to use this installation to play local files you need to install this https://aur.archlinux.org/packages/ffmpeg-compat-57

Removing folder and cloning the folder as in @fuadamaschin suggestion worked for me (I still had to add the key by hand, but it worked fine this time)

I build (and update) my AUR packages usually in the same folder (e.g. ~/build/spotify) with git pull && makepkg -si. After I kept receiving the PGP error I deleted the build folder (rm -rf ~/build/spotify) and cloned the AUR repo again. Then the build with makepkg -si works and the PGP error was gone.

@sawk

Install base-devel.

I did as in NicoHood's comment, but a new error appeared: Cannot find the fakeroot binary.

@DaleYYC I had the same issue. NicoHood's pinned comment at the top of the comments resolved it. https://aur.archlinux.org/packages/spotify/#pinned-747857

==> Validating source files with sha512sums... spotify.protocol ... Passed LICENSE ... Passed spotify-1.1.42.622-Release ... Skipped spotify-1.1.42.622-Release.sig ... Skipped ==> Validating source_x86_64 files with sha512sums... spotify-1.1.42.622-x86_64.deb ... Passed spotify-1.1.42.622-x86_64-Packages ... Passed ==> Verifying source file signatures with gpg... spotify-1.1.42.622-Release ... FAILED (unknown public key D1742AD60D811D58) ==> ERROR: One or more PGP signatures could not be verified!

@renatoliveira thank you for your input. It finally worked for me.

==> ERROR: Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb

--I kept getting this during the download but after spamming to keep trying it after the 5th time it just went through.

I get this error:

==> ERROR: /home/ajzcole/.cache/yay/gobject-introspection-git/gobject-introspection is not a clone of https://gitlab.gnome.org/GNOME/gobject-introspection.git

Clean building does not fix the issue. Neither does a manual wipe of the cache.

EDIT: After installing gtk2 and gobject-introspection manually, everything was fine.

I'm also having issues installing Spotify having followed all the suggestions below to add GPG keys. Here's the output I receive:

curl: (18) transfer closed with 124127740 bytes remaining to read
==> ERROR: Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb

EDIT (16/11/2020): Saw ClickTek's comment to continuously retry. Spotify finally pushed through and installed from cleanbuild.

Just in case someone who has the gpg problems made the same silly mistake I did: I removed ~/.cache/yay/spotify but tried to install spotify-dev. After I removed both, I was able to install the program again.

@techandy1 the difference between PGP and GPG is that one is the private solution developed by Symantec and the other one is the open source implementation. Since GPG is just an implementation of PGP, the correct naming would still be "PGP key".

I'm confused. Deleting the cache did not work for you? I would take a look into the previous 3 or 4 pages in the comments. Some commands were mentioned to clear the cache and reinstall the package.

As for anyone reading this: Spotify changed PGP keys used to sign the package, again. It is using a key that was used before, again. It is necessary to trust that key to install (or ignore signatures during install).

I am having issues with the GPG keys. None of the suggestions below have worked for me. I am still unable to update Spotify. Does anybody else have any suggestions?? I have also noticed that the validpgpkeys have not been updated in the PKGBuild file and also I thought it would be a validgpgkeys and not validpgpkeys????

@kfallah, @bryanOmalley: I also had the same problem. Spotify warning about internet connectivity. I use WireGuard and NetworkManager.

EDIT: Running below should return full, and not limited like it does if I block the connectivity check. If it returns limited Spotify thinks it's offline.

$ nmcli networking connectivity check
full

Anyway, I started logging iptables and adding IP's that was being blocked on different interfaces.

What I found out is that apparently NetworkManager does it's own connectivity checking, which Spotify seems to care about.

On my machine:

/usr/lib/NetworkManager/conf.d/20-connectivity.conf:

[connectivity]
uri=http://www.archlinux.org/check_network_status.txt

NetworkManager uses that address for checking connectivity.

$ curl http://www.archlinux.org/check_network_status.txt
NetworkManager is online

The strange thing was that in Wireshark I noticed that even if I was connected to VPN (WireGuard), requests to 138.201.81.199 (archlinux.org) were being sent over both WireGuard and my normal network card.

My firewall/iptables blocked those requests that did not go over VPN. Strange that it would not only go over my VPN connection all the time.

Anyway, so the solution seems to be, either to disable NetworkManager's connectivity checking altogether. Or watching over you firewall / Wireshark to see if you have the same problem. And if so fixing your firewall.

For now I just allowed 138.201.81.199 on my normal network interface, which iptables previously blocked which Spotify noticed.

iptables -A INPUT -i enp5c8 -s 138.201.81.199 -p tcp --sport 80 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
iptables -A OUTPUT -o enp5c8 -d 138.201.81.199 -p tcp --dport 80 -j ACCEPT

And Spotify have been working since, time will tell if this was the problem.

curl not working anymore. Deleting the cache also didn't work.

@kfallah: I've got the same problem, but nobody talks about any fixes here. It's pretty annoying for me as well.

I've ran into this problem as well with yay:

==> Verifying source file signatures with gpg...
    spotify-1.1.42.622-Release ... FAILED (invalid public key 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45)
==> ERROR: One or more PGP signatures could not be verified!

Tried prety much everything from the previous comments, but nothing worked.

Deleting ~/.cache/yay/spotify before using yay fixed this issue for me.

None of the suggestions below worked for me. I had to reinit pacman keys

mv /etc/pacman.d/gnupg/ /etc/pacman.d/gnupg-bu
pacman-key --init

Credit: Recompiler

Here's a potential solution for the GPG error: gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 8FD3D9A8D3800305A9FFF259D1742AD60D811D58

Make sure you do this on a fresh PKGBUILD and you are fully updated before running this. This worked for me on Manjaro Cinnamon and Manjaro KDE.

To get this to update from the GPG error, the pinned comment didn't work. I took the tip from dymdipi. To make it more clear.

Remove: validpgpkeys=('8FD3D9A8D3800305A9FFF259D1742AD60D811D58') # Spotify <tux@spotify.com>

And add: validpgpkeys=('931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90' '2EBF997C15BDA244B6EBF5D84773BD5E130D1D45') # Spotify <tux@spotify.com>

Hope that helps

After successfully installing 1.1.42.622, is anyone having trouble connecting once you log in? I am constantly offline despite no proxy settings on my machine. I am behind a wireguard VPN. I had to downgrade to 1.1.10.546-4 to fix.

Got it working by modifying the build file as follows:

validpgpkeys=('931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90'
              '2EBF997C15BDA244B6EBF5D84773BD5E130D1D45') # Spotify <tux@spotify.com>
validpgpkeys=('8FD3D9A8D3800305A9FFF259D1742AD60D811D58') # Spotify <tux@spotify.com>

Just an FYI, I imported pubkey_0D811D58.gpg but still got an error (no helpers):

$makepkg -si .... spotify-1.1.42.622-Release ... FAILED (invalid public key 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45)

So I renamed directory and git cloned into a new directory, then ran again with no problems.

I am having the

spotify-1.1.42.622-Release ... FAILED (invalid public key 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45)

Error. How do I do a clean build?

@dymdipi tried importing the new key manually, but still got an error message. seems having yay cleanBuild solved it for me.

@obedmr

You should try this later again. It seems not to be an issue by this PKGBUILD

I just tested this downloadlink, it is working for me/here.

Hi NicoHood,

It's seems like the source url changed or something is blocking the complete download of the .deb file

  -> Downloading spotify-1.1.42.622-x86_64.deb...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  6  120M    6 8249k    0     0  1596k      0  0:01:17  0:00:05  0:01:12 1780k
curl: (18) transfer closed with 117846520 bytes remaining to read
==> ERROR: Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb
    Aborting...
==> ERROR: Makepkg was unable to build spotify.
==> Restart building spotify ? [y/N]
==> --------------------------------

@NicoHood Had the same issue, but following the pinned comment and running a clean reinstall sorted it out.

I'm seeing the same error as gunix. I've tried the pinned comment but still getting the error for:

spotify-1.1.42.622-Release ... FAILED (invalid public key 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45)

If you have performance issues, try to add --disable-gpu to Exec=spotify %U

nano /usr/share/applications/spotify.desktop
Exec=spotify %U --disable-gpu

@0xFFset But at-spi2-atk is a dependency of spotify and atk a dependency of this. How is it possible that you had not installed this?

When playing video podcasts it says they can't be played - the problem actually is missing dependency "atk".

rm -rf $HOME/.cache/yay/spotify fixed it for me after importing the new gpg key

So for me it worked with importing the key from the pinned comment and then do a clean build.

I am getting this error while installing it. Can someone help me? I am on Manjaro.

==> Validating source files with sha512sums...
    spotify.protocol ... Passed
    LICENSE ... Passed
    spotify-1.1.42.622-Release ... Skipped
    spotify-1.1.42.622-Release.sig ... Skipped
==> Validating source_x86_64 files with sha512sums...
    spotify-1.1.42.622-x86_64.deb ... Passed
    spotify-1.1.42.622-x86_64-Packages ... Passed
==> Verifying source file signatures with gpg...
    spotify-1.1.42.622-Release ... FAILED (unknown public key D1742AD60D811D58)
==> ERROR: One or more PGP signatures could not be verified!
Error: Failed to build spotify

Thanks NicoHood

@Meltinglava try a clean build, had the same issue until i did a clean build

It looks like the spotify gpg signing keys has expired. getting:

pub   rsa4096 2018-05-23 [SC] [expired: 2020-08-21]
      931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90
uid           [ expired] Spotify Public Repository Signing Key <tux@spotify.com>

and

pub   rsa4096 2019-07-15 [SC] [expired: 2020-10-07]
      2EBF997C15BDA244B6EBF5D84773BD5E130D1D45
uid           [ expired] Spotify Public Repository Signing Key <tux@spotify.com>

Crashes when clicking on “Add a source” under Local Files (zenity and ffmpeg-compat-57 are installed)

spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)
[1]    68767 segmentation fault (core dumped)  spotify

For me, the only way to solve this was to completely empty the Yay cache with: yay -Sc --aur

Yeah, I had to remove my cache for the build to work with yay as well.

@Alterego: How about to try the recommendation within the pinned comment first?

Having the same issue, not sure what to do

Just a general note, if you use yay, the cache directory you may need to remove is $HOME/.cache/yay/spotify instead.

At least on my systems the Release.sig file wasn't updated therefore, due to the invalid key, not able to validate the Release file, which lead to the process failing.

Maybe there are some issues with the Release signature file being updated correctly sometimes?

weird, yay cannot solve the GPG key import step? I had to simply curl -sS the key, and then yay can install spotify... i'll take a look at yay reported issues

The last upgrade broke it for me:

:: (1/1) Parsing SRCINFO: spotify
==> Making package: spotify 1:1.1.42.622-2 (Mon 19 Oct 2020 11:02:18 PM EEST)
==> Retrieving sources...
  -> Found spotify.protocol
  -> Found LICENSE
  -> Found spotify-1.1.42.622-Release
  -> Found spotify-1.1.42.622-Release.sig
  -> Found spotify-1.1.42.622-x86_64.deb
  -> Found spotify-1.1.42.622-x86_64-Packages
==> Validating source files with sha512sums...
    spotify.protocol ... Passed
    LICENSE ... Passed
    spotify-1.1.42.622-Release ... Skipped
    spotify-1.1.42.622-Release.sig ... Skipped
==> Validating source_x86_64 files with sha512sums...
    spotify-1.1.42.622-x86_64.deb ... Passed
    spotify-1.1.42.622-x86_64-Packages ... Passed
==> Verifying source file signatures with gpg...
    spotify-1.1.42.622-Release ... FAILED (invalid public key 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45)
==> ERROR: One or more PGP signatures could not be verified!
error downloading sources: spotify

Just for a sanity check, I unisntalled the 1.1.42 version, cleared the cache, removed both keys. When using the package manager on Manjaro I still get the unknown public key, but this time it correctly shows the D1742AD60D811D58 key.

Then doing what the pinned comment suggests works just fine too.

I have deleted my previous comments as they mention the other, older, key. Which even though Spotify server's serve it, might not be safe.

If you use aurutils, and got the key via

curl -sS https://download.spotify.com/debian/pubkey_130D1D45.gpg | gpg --import

as suggested, you might need to remove $HOME/.cache/aurutils/sync/spotify before its working.

this is th future proof solution https://bbs.archlinux.org/viewtopic.php?pid=1917184#p1917184

If you get the 'invalid public key' error on Manjaro, you probably have a stale copy of the Release file signed by an expired key in the pamac cache. Delete "/var/tmp/pamac-build-${USER}/spotify" and retry the install.

pubkey_130D1D45.gpg is not documented at Spotify's download page and this reply from two weeks ago also does not mention it. How do you know that the pubkey_130D1D45.gpg is the correct key?

@tengu @arth I cleaned the pacman/yay cache, but still ended up with this error: : (1/1) Parsing SRCINFO: spotify :: PGP keys need importing: -> 8FD3D9A8D3800305A9FFF259D1742AD60D811D58, required by: spotify ==> Import? [Y/n] y :: Importing keys with gpg... gpg: keyserver receive failed: General error problem importing keys

I solved the problem by importing the key manually: gpg --keyserver pool.sks-keyservers.net --recv-keys 8FD3D9A8D3800305A9FFF259D1742AD60D811D58

Thanks @arth, indeed 'yay -Sc --aur' did the trick and spotify is installable now

I have cleaned pacman/yay cache and it works now. (I had the gpg error 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45)

Same as mdedetrich, I get 'Invalid public key' for 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45 every time I try to update spotify

@ManuelFte I have just tried your commands for importing the GPG key and its still failing, I think the GPG key just updated?

I ran into the gpg: keyserver receive failed: General error message and this worked for me:

gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90
echo 'keyserver hkps://keyserver.ubuntu.com' >> ~/.gnupg/gpg.conf

@damonh Please do a cleanbuild. If you're using yay as the helper, when prompted whether you want to do a cleanbuild, choose yes for spotify. Alternatively (or if you don't use an aur helper), you can download the PKGBUILD file and run makepkg -siC in the same directory where the PKGBUILD is.

Trying to update I get this error: spotify-1.1.42.622-Release ... FAILED (invalid public key 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45)

I ran this curl -sS https://download.spotify.com/debian/pubkey_0D811D58.gpg | gpg --import - but it keeps happening.

@knaick I dont understand your question. Sorry for the mistake I meant to ask : @NicoHood any reason for not importing the GPG key you have in the pinned comment inside PKGBUILD script ?? I couldn't run the script before importing the gpg key manually...

I will remove the other old keys now. I have no idea why spotify changes the GPG key so often, this does not give any security benefit at all. Tells us a lot about the company...

I feel your pain.

@knaick I dont understand your question. I will remove the other old keys now. I have no idea why spotify changes the GPG key so often, this does not give any security benefit at all. Tells us a lot about the company...

@NicoHood any reason for not importing the GPG key you have in the pinned comment in the PKGBUILD script ??

:: PGP keys need importing:

-> 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90, required by: spotify

-> 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45, required by: spotify

==> Import? [Y/n]

:: Importing keys with gpg...

gpg: keyserver receive failed: General error problem importing keys

?

Sorry for the delay, guys.

I can confirm that offlinehoster's patches work for me. The only additional problem I had is that the spotify server would close the connection on me, so it took a few tries to download the .deb files. Can download retries be added to PKGBUILD files?

Just going to leave this here for people that are tired of this package having GPG key validity issues and couldn't care less about checking the sources of a package you're downloading on your own network from the official url.

yay -S --mflags --skipinteg spotify

This skips validity checks and just install the music player, use at your own risk!

I just fixed the PKGBUILD by myself.

Just look at https://gist.github.com/offlinehoster/931bd4b3b6b80aa140f563be3df95b22

I checked the GPG fingerprint, the new one, because https://download.spotify.com/debian/pubkey.gpg is not valid anymore. The new one is available at https://download.spotify.com/debian/pubkey_0D811D58.gpg

So i changed the fingerprint inside the PKGBUILD and added a new command to the PKGBUILD to add this key from the spotify URL. And of course, importing the key.

Than I did

makepkg (it took some seconds) and I installed this package with sudo pacman -U spotify-1:1.1.42.622-1-x86_64.pkg.tar.xz

It is working. Maybe you guys @NicoHood can just my gist to push it, so that the package is not out fo date anymore. You can also add me as a Maintainer for the spotify package, https://aur.archlinux.org/account/offlinehoster so I can push it by myself.

It seems that the public key from https://download.spotify.com/debian/pubkey.gpg

is no valid anymore.

pub rsa4096 2019-07-15 [SC] [verfallen: 2020-10-07]

It might help to tell spotify about this, I will do this simply by a tweet on twitter.

@motorlatitude Yes same problem here. "No internet connection detected", have to use the Web Player for now. Anyone found a solution? Or maybe it's something to do with Spotify itself, how they detect internet connection?

Could you add this we package the stable version of Spotify to the description?

I think would make it easier for people to understand.

Adding the public key (@aviallon's comment) to the current PKGBUILD's validpgpkeys and importing both keys from @jal666 comment worked for me

Key 8FD3D9A8D3800305A9FFF259D1742AD60D811D58 needs to be added to the validpgpkeys

curl -sS https://download.spotify.com/debian/pubkey_0D811D58.gpg | gpg --import -

curl -sS https://download.spotify.com/debian/pubkey.gpg | gpg --import -

spotify-1.1.42.622-Release ... FAILED (invalid public key 8FD3D9A8D3800305A9FFF259D1742AD60D811D58)

What @felipec commented. The new key is https://download.spotify.com/debian/pubkey_0D811D58.gpg

You can find it in their Spotify for Linux documentation: https://www.spotify.com/us/download/linux/

Also, for future changes to the PKGBUILD that don't involve a new package version, could you increase pkgrel? According to the Arch Linux wiki: https://wiki.archlinux.org/index.php/PKGBUILD#pkgrel

The release number. This is usually a positive integer number that allows to differentiate between consecutive builds of the same version of a package. As fixes and additional features are added to the PKGBUILD that influence the resulting package, the pkgrel should be incremented by 1. When a new version of the software is released, this value must be reset to 1.

You still need to modify validpgpkeys.

validpgpkeys=('8FD3D9A8D3800305A9FFF259D1742AD60D811D58') # Spotify <tux@spotify.com>

@NicoHood : I just tested it, no. It says unknown key D1742AD60D811D58 and it's not installing because of PGP signature is missing

=> Überprüfe Signaturen der Quell-Dateien mit gpg... spotify-1.1.42.622-Release ... FEHLGESCHLAGEN (Unbekannter öffentlicher Schlüssel D1742AD60D811D58) ==> FEHLER: Eine oder mehrere PGP-Signaturen konnten nicht überprüft werden!

I've updated the package. Does it build now for you guys?

@motorlatitude I have the same issue

@milaxnuts Thanks, that worked for me also.

@motorlatitude Yes I am having that issue

Anybody having issues with spotify going offline whilst using a VPN? The previous version worked fine

@milaxnuts worked perfectly. Thanks

I had to curl -sS https://download.spotify.com/debian/pubkey_0D811D58.gpg | gpg --import - to get it working. In addition to patch the PKGBUILD as in @milaxnuts' workaround

@milaxnuts' workaround works fine here. But it crashes when trying to do anything that involves the file chooser. (Changing playlist artwork/Managing local music, etc) Can anyone help with that?

current workaround for spotify-1.1.42.622-Release ... FAILED

cd ~/.cache/yay/spotify # or wherever ..
cp PKGBUILD PKGBUILD.bak

# patch checksum of spotify-1.1.42.622-Release
sed -i -E "s/'70ff7e4e90e2aa96[^']+'/'d640af1e310c3bd1d198\
0b7629ea0ccb2c2a0476d14d2fc05d2d835b0994f7e5ab9d769adcbec0\
d354dddb13c20a4813fad6f3220b38787b3ace744fefd47851'/" PKGBUILD

# patch gpg key
perl -i -p0e "s/(validpgpkeys=\()[^)]+\)/\$1'8FD3D9A8D38003\
05A9FFF259D1742AD60D811D58')/smg" PKGBUILD

# install gpg key
curl -sS https://download.spotify.com/debian/pubkey_0D811D58.gpg \
| gpg --import -

# install spotify
makepkg -si

Acquiring the deb file appears to require a client that will resume the download until the full file is acquired:

$ wget http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb
--2020-10-10 15:29:26--  http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb
Resolving repository.spotify.com (repository.spotify.com)... 13.33.155.22, 13.33.155.135, 13.33.155.206, ...
Connecting to repository.spotify.com (repository.spotify.com)|13.33.155.22|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 126293582 (120M) [application/octet-stream]
Saving to: ‘spotify-client_1.1.42.622.gbd112320-37_amd64.deb’

spotify-client_1.1.42.622.gbd1123   1%[>                                                            ]   2.07M   528KB/s    in 4.8s    

2020-10-10 15:29:31 (444 KB/s) - Connection closed at byte 2165843. Retrying.

--2020-10-10 15:29:32--  (try: 2)  http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb
Connecting to repository.spotify.com (repository.spotify.com)|13.33.155.22|:80... connected.
HTTP request sent, awaiting response... 206 Partial Content
Length: 126293582 (120M), 124127739 (118M) remaining [application/octet-stream]
Saving to: ‘spotify-client_1.1.42.622.gbd112320-37_amd64.deb’

spotify-client_1.1.42.622.gbd1123   3%[+>                                                           ]   3.96M   475KB/s    in 4.8s    

2020-10-10 15:29:37 (407 KB/s) - Connection closed at byte 4148750. Retrying.

--2020-10-10 15:29:39--  (try: 3)  http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb
Connecting to repository.spotify.com (repository.spotify.com)|13.33.155.22|:80... connected.
HTTP request sent, awaiting response... 206 Partial Content
Length: 126293582 (120M), 122144832 (116M) remaining [application/octet-stream]
Saving to: ‘spotify-client_1.1.42.622.gbd112320-37_amd64.deb’

spotify-client_1.1.42.622.gbd1123   4%[++                                                           ]   5.07M   238KB/s    in 4.8s    

2020-10-10 15:29:44 (238 KB/s) - Connection closed at byte 5311530. Retrying.

--2020-10-10 15:29:47--  (try: 4)  http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb
Connecting to repository.spotify.com (repository.spotify.com)|13.33.155.22|:80... connected.
HTTP request sent, awaiting response... 206 Partial Content
Length: 126293582 (120M), 120982052 (115M) remaining [application/octet-stream]
Saving to: ‘spotify-client_1.1.42.622.gbd112320-37_amd64.deb’

spotify-client_1.1.42.622.gbd1123 100%[++==========================================================>] 120.44M  17.7MB/s    in 6.6s    

2020-10-10 15:29:54 (17.5 MB/s) - ‘spotify-client_1.1.42.622.gbd112320-37_amd64.deb’ saved [126293582/126293582]

$ sha512sum spotify-client_1.1.42.622.gbd112320-37_amd64.deb 
a3fe98d69460ffd641df3219c2a3d164a33e2b52c86a56276e473dd5c3a43d6304df3b77fefcf0ca6c09cb6e2c8dacab65573cf7543725b6c8d402832149e122  spotify-client_1.1.42.622.gbd112320-37_amd64.deb

Their repository has an issue, I cannot directly download the whole file from Firefox either.

Errors I'm getting...

curl: (18) transfer closed with 39884450 bytes remaining to read

==> ERROR: Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb

and after attempting to get it to download multiple times, I will get this...

==> Validating source files with sha512sums...

spotify.protocol ... Passed

LICENSE ... Passed

spotify-1.1.42.622-Release ... FAILED

spotify-1.1.42.622-Release.sig ... Skipped

==> ERROR: One or more files did not pass the validity check!

The checksum for spotify-1.1.42.622-Release appears to be incorrect after the latest update.

anybody using alsa? it is broken for me with it

Dragonek93 did you follow the steps of prismex (navidagz and FDotLung)? Import the GPG key as suggested by navidagz:

curl -sS https://download.spotify.com/debian/pubkey_0D811D58.gpg | gpg --import -

sha512sums=('999abe46766a4101e27477f5c9f69394a4bb5c097e2e048ec2c6cb93dfa1743eb436bde3768af6ba1b90eaac78ea8589d82e621f9cbe7d9ab3f41acee6e8ca20'
            '2e16f7c7b09e9ecefaa11ab38eb7a792c62ae6f33d95ab1ff46d68995316324d8c5287b0d9ce142d1cf15158e61f594e930260abb8155467af8bc25779960615'
            'd640af1e310c3bd1d1980b7629ea0ccb2c2a0476d14d2fc05d2d835b0994f7e5ab9d769adcbec0d354dddb13c20a4813fad6f3220b38787b3ace744fefd47851'
            '45d46190865f67cc4fc88884d26ed9645c98710c4da6ac361e9b5a90662ae3a9570defaeeda67ec8bc3fb2e00a3de9d5a4a8c20568b0b5ed56228c2bb06769e5')
sha512sums_x86_64=('a3fe98d69460ffd641df3219c2a3d164a33e2b52c86a56276e473dd5c3a43d6304df3b77fefcf0ca6c09cb6e2c8dacab65573cf7543725b6c8d402832149e122'
                   'af7eb8c50e003638cab04ef1cad36f43379e678a1071c65844a6ff8963434b427044b76159e51c1383698c309c814261ed85aab02ffb86ac73ee86181aada5e9')
validpgpkeys=('931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90'
              '2EBF997C15BDA244B6EBF5D84773BD5E130D1D45') # Spotify tux@spotify.com
validpgpkeys=('8FD3D9A8D3800305A9FFF259D1742AD60D811D58') # Spotify tux@spotify.com

i dont know why i cant download spotify. Key is downloaded and if im at last step i mean checking packages i got error and installing is canceled: "one of the files isnt correct. How to repair this problem because i dont like flatpak version or snap. The same problem is if i try to download aur pkg and install manual by commang makepkg -si.

I'm still getting this after updating the checksums and importing the latest GPG key

==> Verifying source file signatures with gpg...
    spotify-1.1.42.622-Release ... FAILED (invalid public key 8FD3D9A8D3800305A9FFF259D1742AD60D811D58)

EDIT: This is the key I have imported

EDIT2: Ah, you must also be sure to add the new GPG key to the PKGBUILD as well

pub   rsa4096 2020-09-08 [SC] [expires: 2021-12-02]
      8FD3 D9A8 D380 0305 A9FF  F259 D174 2AD6 0D81 1D58
uid           [ unknown] Spotify Public Repository Signing Key <tux@spotify.com>

The pubkey.gpg expired yesterday. You can get a current one with:

curl -sS https://download.spotify.com/debian/pubkey_0D811D58.gpg | gpg --import -

as stated on https://www.spotify.com/de/download/linux/

The changes to the PKGBUILD of navidagz then worked. You have to delete the lines with - in front of it and add the lines with +, like for a git diff. Why are those changes not in the PKGBUILD from the beginning though?

The hints of navidagz and FDotLung did the trick. Import the GPG key as navidagz explains and copy the hashes of FDotLung - as the hashes of navidagz contain illegal syntax.

The SHA512 hashes and GPG keys should be as follows:

sha512sums=('999abe46766a4101e27477f5c9f69394a4bb5c097e2e048ec2c6cb93dfa1743eb436bde3768af6ba1b90eaac78ea8589d82e621f9cbe7d9ab3f41acee6e8ca20'
            '2e16f7c7b09e9ecefaa11ab38eb7a792c62ae6f33d95ab1ff46d68995316324d8c5287b0d9ce142d1cf15158e61f594e930260abb8155467af8bc25779960615'
            'd640af1e310c3bd1d1980b7629ea0ccb2c2a0476d14d2fc05d2d835b0994f7e5ab9d769adcbec0d354dddb13c20a4813fad6f3220b38787b3ace744fefd47851'
            '45d46190865f67cc4fc88884d26ed9645c98710c4da6ac361e9b5a90662ae3a9570defaeeda67ec8bc3fb2e00a3de9d5a4a8c20568b0b5ed56228c2bb06769e5')
sha512sums_x86_64=('a3fe98d69460ffd641df3219c2a3d164a33e2b52c86a56276e473dd5c3a43d6304df3b77fefcf0ca6c09cb6e2c8dacab65573cf7543725b6c8d402832149e122'
                   'af7eb8c50e003638cab04ef1cad36f43379e678a1071c65844a6ff8963434b427044b76159e51c1383698c309c814261ed85aab02ffb86ac73ee86181aada5e9')
validpgpkeys=('931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90'
              '2EBF997C15BDA244B6EBF5D84773BD5E130D1D45') # Spotify <tux@spotify.com>
validpgpkeys=('8FD3D9A8D3800305A9FFF259D1742AD60D811D58') # Spotify <tux@spotify.com>

For those who have a problem with validity check, import the this GPG key:

curl -sS https://download.spotify.com/debian/pubkey_0D811D58.gpg | gpg --import -

Then edit the PKGBUILD like below:

 sha512sums=('999abe46766a4101e27477f5c9f69394a4bb5c097e2e048ec2c6cb93dfa1743eb436bde3768af6ba1b90eaac78ea8589d82e621f9cbe7d9ab3f41acee6e8ca20'
             '2e16f7c7b09e9ecefaa11ab38eb7a792c62ae6f33d95ab1ff46d68995316324d8c5287b0d9ce142d1cf15158e61f594e930260abb8155467af8bc25779960615'
-            '70ff7e4e90e2aa96c1a1ff9cb4e09d86852c2fff7fa5a8acf58c3c36fd081bb190e0e1de09f2c77bc1f7c792c3ea33612e709d2f2ac3f5a0e6bb9bcbd6ada37b'
+            'd640af1e310c3bd1d1980b7629ea0ccb2c2a0476d14d2fc05d2d835b0994f7e5ab9d769adcbec0d354dddb13c20a4813fad6f3220b38787b3ace744fefd47851'
             'SKIP')
 sha512sums_x86_64=('a3fe98d69460ffd641df3219c2a3d164a33e2b52c86a56276e473dd5c3a43d6304df3b77fefcf0ca6c09cb6e2c8dacab65573cf7543725b6c8d402832149e122'
                    'af7eb8c50e003638cab04ef1cad36f43379e678a1071c65844a6ff8963434b427044b76159e51c1383698c309c814261ed85aab02ffb86ac73ee86181aada5e9')
-validpgpkeys=('931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90'
-              '2EBF997C15BDA244B6EBF5D84773BD5E130D1D45') # Spotify <tux@spotify.com>
+validpgpkeys=('8FD3D9A8D3800305A9FFF259D1742AD60D811D58') # Spotify <tux@spotify.com>

I have the same error as @anatolik. I could still install the package fine yesterday.

I've got an error while building this package:

==> Retrieving sources...
  -> Found spotify.protocol
  -> Found LICENSE
  -> Downloading spotify-1.1.42.622-Release...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  2434  100  2434    0     0   7055      0 --:--:-- --:--:-- --:--:--  7075
  -> Downloading spotify-1.1.42.622-Release.sig...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   833  100   833    0     0   2586      0 --:--:-- --:--:-- --:--:--  2586
  -> Downloading spotify-1.1.42.622-x86_64.deb...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  120M  100  120M    0     0  23.9M      0  0:00:05  0:00:05 --:--:-- 24.2M
  -> Downloading spotify-1.1.42.622-x86_64-Packages...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  4206  100  4206    0     0  13611      0 --:--:-- --:--:-- --:--:-- 13567
==> Validating source files with sha512sums...
    spotify.protocol ... Passed
    LICENSE ... Passed
    spotify-1.1.42.622-Release ... FAILED
    spotify-1.1.42.622-Release.sig ... Skipped
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Could not download sources.

I imported the gpg key from the pinned comment. gpg --list-keys gives the following output:

pub   rsa4096 2019-07-15 [SC] [expires: 2020-10-07]
      2EBF997C15BDA244B6EBF5D84773BD5E130D1D45
uid           [ unknown] Spotify Public Repository Signing Key tux@spotify.com

diff --git a/PKGBUILD b/PKGBUILD
index aa7b940..1c8d7ae 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -36,12 +36,11 @@ source_x86_64=("${pkgname}-${pkgver}-x86_64.deb::http://repository.spotify.com/p
 #              "${pkgname}-${pkgver}-i686-Packages::http://repository.spotify.com/dists/stable/non-free/binary-i386/Packages")
 sha512sums=('999abe46766a4101e27477f5c9f69394a4bb5c097e2e048ec2c6cb93dfa1743eb436bde3768af6ba1b90eaac78ea8589d82e621f9cbe7d9ab3f41acee6e8ca20'
             '2e16f7c7b09e9ecefaa11ab38eb7a792c62ae6f33d95ab1ff46d68995316324d8c5287b0d9ce142d1cf15158e61f594e930260abb8155467af8bc25779960615'
-            '70ff7e4e90e2aa96c1a1ff9cb4e09d86852c2fff7fa5a8acf58c3c36fd081bb190e0e1de09f2c77bc1f7c792c3ea33612e709d2f2ac3f5a0e6bb9bcbd6ada37b'
+            'd640af1e310c3bd1d1980b7629ea0ccb2c2a0476d14d2fc05d2d835b0994f7e5ab9d769adcbec0d354dddb13c20a4813fad6f3220b38787b3ace744fefd47851'
             'SKIP')
 sha512sums_x86_64=('a3fe98d69460ffd641df3219c2a3d164a33e2b52c86a56276e473dd5c3a43d6304df3b77fefcf0ca6c09cb6e2c8dacab65573cf7543725b6c8d402832149e122'
                    'af7eb8c50e003638cab04ef1cad36f43379e678a1071c65844a6ff8963434b427044b76159e51c1383698c309c814261ed85aab02ffb86ac73ee86181aada5e9')
-validpgpkeys=('931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90'
-              '2EBF997C15BDA244B6EBF5D84773BD5E130D1D45') # Spotify tux@spotify.com
+validpgpkeys=('8FD3D9A8D3800305A9FFF259D1742AD60D811D58') # Spotify tux@spotify.com

# Spotify uses different names for the arch
 if [ "${CARCH}" = "i686" ]; then

Building spotify...
==> Making package: spotify 1:1.1.42.622-1 (Tuesday 06 October 2020 05:22:02 AM)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found spotify.protocol
  -> Found LICENSE
  -> Found spotify-1.1.42.622-Release
  -> Found spotify-1.1.42.622-Release.sig
  -> Found spotify-1.1.42.622-x86_64.deb
  -> Found spotify-1.1.42.622-x86_64-Packages
==> Validating source files with sha512sums...
    spotify.protocol ... Passed
    LICENSE ... Passed
    spotify-1.1.42.622-Release ... Passed
    spotify-1.1.42.622-Release.sig ... Skipped
==> Validating source_x86_64 files with sha512sums...
    spotify-1.1.42.622-x86_64.deb ... Passed
    spotify-1.1.42.622-x86_64-Packages ... Passed
==> Verifying source file signatures with gpg...
    spotify-1.1.42.622-Release ... FAILED (unknown public key D1742AD60D811D58)
==> ERROR: One or more PGP signatures could not be verified!
Failed to build spotify

To fix the package, update your Spotify GPG key using the instructions in the pinned comment and then apply the following patch to the PKGBUILD:

@@ -36,12 +36,11 @@
 #              "${pkgname}-${pkgver}-i686-Packages::http://repository.spotify.com/dists/stable/non-free/binary-i386/Packages")
 sha512sums=('999abe46766a4101e27477f5c9f69394a4bb5c097e2e048ec2c6cb93dfa1743eb436bde3768af6ba1b90eaac78ea8589d82e621f9cbe7d9ab3f41acee6e8ca20'
             '2e16f7c7b09e9ecefaa11ab38eb7a792c62ae6f33d95ab1ff46d68995316324d8c5287b0d9ce142d1cf15158e61f594e930260abb8155467af8bc25779960615'
-            '70ff7e4e90e2aa96c1a1ff9cb4e09d86852c2fff7fa5a8acf58c3c36fd081bb190e0e1de09f2c77bc1f7c792c3ea33612e709d2f2ac3f5a0e6bb9bcbd6ada37b'
+            'd640af1e310c3bd1d1980b7629ea0ccb2c2a0476d14d2fc05d2d835b0994f7e5ab9d769adcbec0d354dddb13c20a4813fad6f3220b38787b3ace744fefd47851'
             'SKIP')
 sha512sums_x86_64=('a3fe98d69460ffd641df3219c2a3d164a33e2b52c86a56276e473dd5c3a43d6304df3b77fefcf0ca6c09cb6e2c8dacab65573cf7543725b6c8d402832149e122'
                    'af7eb8c50e003638cab04ef1cad36f43379e678a1071c65844a6ff8963434b427044b76159e51c1383698c309c814261ed85aab02ffb86ac73ee86181aada5e9')
-validpgpkeys=('931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90'
-              '2EBF997C15BDA244B6EBF5D84773BD5E130D1D45') # Spotify <tux@spotify.com>
+validpgpkeys=('8FD3D9A8D3800305A9FFF259D1742AD60D811D58') # Spotify <tux@spotify.com>

 # Spotify uses different names for the arch
 if [ "${CARCH}" = "i686" ]; then

Currently the spotify-1.1.42.622-Release signature is failing.

$ makepkg 
==> Making package: spotify 1:1.1.42.622-1 (Mon 05 Oct 2020 08:30:07 AM AKDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found spotify.protocol
  -> Found LICENSE
  -> Found spotify-1.1.42.622-Release
  -> Found spotify-1.1.42.622-Release.sig
  -> Found spotify-1.1.42.622-x86_64.deb
  -> Found spotify-1.1.42.622-x86_64-Packages
==> Validating source files with sha512sums...
    spotify.protocol ... Passed
    LICENSE ... Passed
    spotify-1.1.42.622-Release ... Passed
    spotify-1.1.42.622-Release.sig ... Skipped
==> Validating source_x86_64 files with sha512sums...
    spotify-1.1.42.622-x86_64.deb ... Passed
    spotify-1.1.42.622-x86_64-Packages ... Passed
==> Verifying source file signatures with gpg...
    spotify-1.1.42.622-Release ... FAILED (invalid public key 8FD3D9A8D3800305A9FFF259D1742AD60D811D58)
==> ERROR: One or more PGP signatures could not be verified!

@Simone98RC I also had UI freezes long time ago on KDE when using Spotify. The problem was graphic driver - I used nouveau. After proprietary NVIDIA driver installation freezes were gone, so I use Spotify on KDE - including current version - without any issues.

@Simone98RC I don't encounter any of the effects you describe (I also didn't remove any config/cache files. Only difference is I'm running Gnome 3.36 as DE

Since latest update I encounter many UI freezes, I can interact only via KDE media player with play/pause/forward/reverse commands.

Obviously I've tried to delete Spotify configuration in both ".config" and ".cache" directories.

I strongly suggest to revert previous version (v1.1.41.634).

I just emailed tux@spotify.com this:

Subject: GPG Key Expired

Body: See https://aur.archlinux.org/packages/spotify/#comment-768314, please leave a comment on the AUR link to let everyone know the new key. 

@oczonuewe Thanks for the tips, I checked my spotify.desktop and the argument is already there

I'm using GNOME with gnome-keyring installed and working, either they broke the compatibility or my system is acting weird

@barkbork I've updated Spotify to to 1.1.42.622, I use Manjaro KDE with autologin. Now when I run Spotify KWalletManager asks me for password but everything works fine. Maybe you have system's password manager (kdewallet or seahorse or derivative) or autologin not configured properly? Or maybe you haven't %u argument in spotify desktop file? Without that I had similar problems.

Just updated to 1.1.42.622, it seems Spotify has forgotten how to store things in files : every time I close Spotify and open it again, I need to re-enter my credentials

I don't know if the music cache is storing anything or if this bug affects only the login, but it seems like a regression of some sort

Just updated to 1.1.42.622 and I cannot launch spotify anymore:

$ spotify 
spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)
[1001/103235.173021:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.
Trace/breakpoint trap (core dumped)

I managed to fix my key errors by running

gpg --keyserver hkp://keyserver.ubuntu.com --receive-keys 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90

The key is expired, but works

» gpg --keyserver hkp://pool.sks-keyservers.net --search-keys 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90
gpg: data source: http://62.75.158.38:11371
(1) Spotify Public Repository Signing Key <tux@spotify.com>
      4096 bit RSA key A87FF9DF48BF1C90, created: 2018-05-23, expires: 2020-08-21 (expired)

It looks like one of the PGP keys have expired recently

@belzebub40k thanks for the note!

I've updated the spotify version. But please be aware that all local stored music along with your remembered password will be lost. Spotify will ask for your password again and the music will be downloaded again.

I am not sure what happens with the old downloaded music, if it will be cleared. Maybe someone can have a look at it and report us the results?

As always: If there is any problem with the package, please let me know.

Spotify released a new stable version 1.1.42.622.gbd112320-37 (listed in dists/stable/non-free/binary-amd64/Packages)

http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.42.622.gbd112320-37_amd64.deb

Goodnight. The version 1.1.10.546 of spotify was removed from the http://repository.spotify.com/pool/non-free/s/spotify-client/

To those with the error:
==> Validating source_x86_64 files with sha512sums...
spotify-1.1.10.546-x86_64.deb ... Passed
spotify-1.1.10.546-x86_64-Packages ... FAILED
==> ERROR: One or more files did not pass the validity check!
This is due to a new stable version being released.
In the meantime you can either edit the pkgbuild and set the correct shasum or run:
yay -G spotify
cd spotify
makepkg --skipchecksums

Running

makepkg -si returns

==> Validating source files with sha512sums... spotify.protocol ... Passed LICENSE ... Passed spotify-1.1.10.546-Release ... Skipped spotify-1.1.10.546-Release.sig ... Skipped ==> Validating source_x86_64 files with sha512sums... spotify-1.1.10.546-x86_64.deb ... Passed spotify-1.1.10.546-x86_64-Packages ... FAILED ==> ERROR: One or more files did not pass the validity check!

Pinned comment does not fix.

==> Validating source_x86_64 files with sha512sums...
    spotify-1.1.10.546-x86_64.deb ... Passed
    spotify-1.1.10.546-x86_64-Packages ... FAILED
==> ERROR: One or more files did not pass the validity check!

I got this errors when downloading it, with already the gpg key.

:: PGP keys need importing: -> 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90, required by: spotify ==> Import? [Y/n] :: Importing keys with gpg... gpg: keyserver receive failed: General error problem importing keys

Hi, I see the following errors in the terminal when launching spotify:

$ spotify 
spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)
[0926/220340.657547:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command

Any tips ?

does anyone else have problems playing audio lately?

http://repository.spotify.com/pool/non-free/s/spotify-client/

spotify-client_1.1.42.622.gbd112320-37_amd64.deb

sha512sum = a3fe98d69460ffd641df3219c2a3d164a33e2b52c86a56276e473dd5c3a43d6304df3b77fefcf0ca6c09cb6e2c8dacab65573cf7543725b6c8d402832149e122

Both SnapCraft and Flathub have the latest versions

Can't download the deb file. Try from web browser but download failed.

curl: (18) transfer closed with 47214726 bytes remaining to read ==> ERROR: Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.10.546.ge08ef575-19_amd64.deb Aborting... :: Unable to build spotify - makepkg exited with code: 1 =>> Try again? [y/N]: ^C

$ curl http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.10.546.ge08ef575-19_amd64.deb --output spotify-client_1.1.10.546.ge08ef575-19_amd64.deb % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 1 109M 1 1451k 0 0 277k 0 0:06:44 0:00:05 0:06:39 324k curl: (18) transfer closed with 113488816 bytes remaining to read

Seems there is a new version for the deb file on the repo :

spotify-client_1.1.26.501.gbe11e53b-15_amd64.deb 19-Feb-2020 12:36 120102446

Failed too

==> Verifying source file signatures with gpg... spotify-1.1.10.546-Release ... FAILED (unknown public key 4773BD5E130D1D45) ==> ERROR: One or more PGP signatures could not be verified! Failed to build spotify

spotify 1.1.26.501.gbe11e53b-15 from Spotify✓ installed

@kaipee2 this is the output of installing from snap. I can't seem to get it to work this way though.

@dragonsawareness this package is not Out of Date.

The version identified by yourself does not exist in any official Spotify repo, even their own latest testing is nowhere near that version number

curl -v --silent https://repository-origin.spotify.com/dists/testing/non-free/binary-amd64/Packages 2>&1 | grep Version
Version: 1:1.1.10.546.ge08ef575-19

1.1.26.501.gbe11e53b-15 is latest version from snap store. But not lastest by far in repo list. Someone bug spotify?

The spotify package cannot be downloaded

ERROR: Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.10.546.ge08ef575-19_amd64.deb Aborting...

When I go to the link, I download it, and it also fails around 4MB in.

All who are still having key issues with the second key, try this:

gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90

All who are still having key issues with the second key, try this:

gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90

@MrDread I have both of those packages installed already and it does not work. I forgot to mention zenity in the list of packages I have, but I did say I have ffmpeg-compat-57.

@gshinguji "If you wish to play local files you will need to additionally install zenity and ffmpeg-compat-57AUR." from wiki

@gshinguji "If you wish to play local files you will need to additionally install zenity and ffmpeg-compat-57AUR." from wiki

Local files refuse to play. I have x264, x265, ffmpeg, and ffmpeg-compat-57 installed. When I tried running "downgrade x264 ffmpeg" which was suggested earlier, I had dependency errors trying to downgrade ffmpeg, along with x264 not even downgrading. I have tried rebuilding all of these packages to no avail. I still get the same "Spotify can't play this right now."

@Energi yes, i know i can just say "n" and install it, but it shouldn't be asking to install this key at all.

@lemagicien Do you disagree with the pinned comment?

@AWhetter @NicoHood Hey guys. Any need for co-maintainers to keep the package up to date?

==> Verifying source file signatures with gpg...
    spotify-1.1.10.546-Release ... FAILED (unknown public key 4773BD5E130D1D45)
==> ERROR: One or more PGP signatures could not be verified!

@sTiKyt Just do not import this (931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90) key, tested it myself - installs fine without it.

@huyhoang8398 same. Before it was asking for 2 keys, i did curl -sS https://download.spotify.com/debian/pubkey.gpg | gpg --import -

And now it's only asking for 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90, which doesn't import if i enter "Y", obviously...

@NicoHood I did import spotify gpg key but while installing via yay they're still asking for this gpg key 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90

@bjo Thanks for the suggestion. But I use spotify without internet some time. I'll start gathering MP3s again.

@E3LDDfrK If you are too annoyed by the software itself, you can use https://open.spotify.com and connect it to spotifyd which is also able to run on headless boxes.

@andrhua Thanks for the info. It's the same with my spotify. I really should start to leave this service, too much annoyances on Linux. Still grateful though that some of Spotify's engineers took their time for this.

Solution: rebuild ffmpeg-compat-57

Just wanted to add, I was able to install by using the pinned comment and installing it from the spotify-dev provider. When it asked to to import keys with gpg I declined

I was able to install by manually importing the gpg keys, but this needs to be fixed in the PKGBUILD.

Seems like ffmpeg 2:4.3.1-2 breaks local files playback. downgrade x264 ffmpeg unbreaks it

@smittie thanks for the workround!

@smittie It worked thanks!

I've imported the missing keys like that: gpg --keyserver pool.sks-keyservers.net --recv-keys 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45

The PKGBUILD seems to be fine but for some reason the server terminates the .deb download before it completes. I managed to install from yay by entering the command repeatedly and downloading a portion of the file each time (don't do a clean build in your subsequent attempts).

@bus That does not work for me and others (see my comment posted 2020-07-08 10:04).

gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90
gpg: keyserver receive failed: Server indicated a failure

That key returns a 404 using that keyserver.

You can import the missing key with this command:

gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90

Absolutely not the best way to do it, but if you're really desperate (like me), you can install it the old way (without yay or yaourt), edit the pkgbuild to remove the verification and makepkg -si it. Worked for me.

@NicoHood, I would like to inform you that the GPG key "931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90" is expired (As @jmckind shows here) and now, even the one in the pinned post imports only one key. Hence the mentioned key should be removed from the PKGBUILD file (causes a bit of confusion with yay, when it asks to install missing GPG keys and then fails.).

@jmckind I am experiencing the same issue

Basically, https://www.spotify.com/de/download/linux/ mentions two ways to install spotify. Snap and deb package. The snap version is currently 1.1.26, and newer than the latest deb package which is 1:1.1.10. I think we can just wait until spotify officially offers a newer deb package.

And this is just personal observation. But a lot of posts on spotify's linux forum is about the problems with the snap package. So I'd guess the version 1.1.26 is pretty buggy. Could be a snap issue though.

@TanishqTejaswi I am just a normal user of this package, but your explanation does sound convincing to me.

It would be good if the maintainer could perhaps clarify the current situation regarding this package and if we should expect an update anytime soon (if necessary).

The link pinned at top, which is http://repository.spotify.com/dists/stable/non-free/binary-amd64/Packages, has info about the stable version and the following link has info about the testing version: http://repository.spotify.com/dists/testing/non-free/binary-amd64/Packages

However, the version number in both the links is the same, i.e., 1:1.1.10.546.ge08ef575-19. So, I suspect they have not updated these links since long, even though they have kept updating the package.

Seriously, if you don't know how branches work don't go flagging packages as out of date. Smh.

The flagger claims that the current version is 1.1.26.501 but the link to the stable versions in the pinned comment by the maintainer says its 1.1.10.546 (an older version). So it seems like the testing version was confused for the stable version again. False alarm?

curl -sS https://download.spotify.com/debian/pubkey.gpg | gpg --import -
yay -Syu spotify
yay -Syu

Still flags spotify as outdated.

I ran the command to import the GPG key, which worked for one of the two keys I am missing but I am still getting this error. What am I doing wrong here?

==> PGP keys need importing:
 -> 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90, required by: spotify
==> Import? [Y/n] 
:: Importing keys with gpg...
gpg: keyserver receive failed: Server indicated a failure
problem importing keys

When I search for that key on the ubuntu keyserver search page I get "Not Found". Did they recycle the key again and now this one is no longer available?

http://keyserver.ubuntu.com/pks/lookup?search=931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90&fingerprint=on&op=index

@cirlo

Anyhow it should be changed to exec=spotify --uri="%u" as specified in the help page and in the above mentioned support page.

I couldn't find the help page and support page saying that.

Currently my spotify.desktop for XFCE has the line Exec=spotify %U with a capital "U".

I don't really know what's the purpose of the spotify.protocol in KDE, I can't find much (but I imagine its only intention is to open an URI, (although with some problems)[https://community.spotify.com/t5/Desktop-Linux/Linux-Spotify-URI-only-opens-start-page/m-p/1675578#M1812]).

Anyhow it should be changed to exec=spotify --uri="%u" as specified in the help page and in the above mentioned support page.

@agm28011997 Honestly, a lot of the posts in the spotify forum are about problems caused by installing the snap package. So, the 1.1.26 version used in snap is probably problematic.

https://community.spotify.com/t5/Live-Ideas/Desktop-Linux-Desktop-App-Minimize-to-taskbar-or-system-tray/idi-p/4804945 if you don't mind I'm going to spam this to see if there is some help! tray icon on Linux upvote pls!

@E3LDDfrK mine only problem with spotify is the no tray icon XD.. so... but if the people wants the newer version okey, let's try.

PLS I WANT TRAY! and want spotify in community too..

One change in the newer version (1.1.26) seems to be the checkbox to turn off the automix/-dj feature. According to https://community.spotify.com/t5/Desktop-Linux/Spotify-repo-not-updating/td-p/4974323

I would be where we were, because the snap comes with all things needed..the deb is more the wild

agm28011997, I have tried the Snap package, and it works OK.

I do not know what is new in the latest version.

Here is a screenshot of the Snap package information, in Pamac:

https://snipboard.io/tLFJYg.jpg

@johnprogrammer have you tried the snap or not? Is there something new in that package or not? This change log is useless xD

@agm28011997, I found a Spotify changelog here:

https://fedora.pkgs.org/31/rpmfusion-nonfree-updates-x86_64/lpf-spotify-client-1.1.26.501-1.fc31.x86_64.rpm.html

2020-04-27 - Sérgio Basto sergio@serjux.com - 1.1.26.501-1 - Update to 1.1.26.501.gbe11e53b

2019-10-18 - Sérgio Basto sergio@serjux.com - 1.1.10.546-3 - Fix commit of spotify-make in spotify-client.spec.in

2019-09-28 - Sérgio Basto sergio@serjux.com - 1.1.10.546-2 - Update spotify-make rfbz#5395

2019-07-25 - Leigh Scott leigh123linux@gmail.com - 1.1.10.546-1 - Update to 1.1.10.546.ge08ef575

The stable version of the spotify client seems to be 1.1.26.501 which is also the version of the community spotify-client package in OpenSUSE Thumbleweed.

@johnprogrammer what's new in that version? I ask because if is no new thing i prefer stay with that version right now. I don't know the opinion of nico..

BTW https://community.spotify.com/t5/Live-Ideas/Linux-Add-Spotify-to-the-official-Linux-repositories/idi-p/4813156 can you enter this idea in spotify? I cant...

@agm28011997, I am just a user of Spotify, I am not involved in its development.

I know that spotify-client_1.1.26.501.gbe11e53b-15_amd64.deb is the latest version, because it is the same version number, with the official Snap package.

I am using Manjaro, and Pamac, its graphical package manager, works with Snap too, it has a Snap plugin.

And I checked the Spotify Snap package, to see if it works OK in my PC. It worked, but I do not like Snap packages a lot, I prefer AUR packages.

https://community.spotify.com/t5/Live-Ideas/Redistribute-Spotify-on-Linux-Distributions/idi-p/1695334/page/25#comments

@nicohood and what happened to this? it's incredible the little priority linux has for everybody that tasks that are little as say " yes" to something or things like putting # in some place in the code to improve Linux behaviour are sooo ignored...

I have to say that.. I would have spotify-qt client official one of older version because for me worked much better than this newer ones.. But I think is not possible nowadays in arch, right?

Example: the older predark version had tray icon.. soemthing that this newer electron based huge package app, not XD... @nicohood have you tried for example another app like deezer? I have tried this and It feels like I am going to change..

I wish this topic survives and the developpers come back this thing to post dark version with a tweak in options inside the app : https://community.spotify.com/t5/Live-Ideas/Desktop-Linux-Desktop-App-Minimize-to-taskbar-or-system-tray/idi-p/4804945

okey @johnprogrammer but what have the newer version than the older ones?

I ask because I prefer not to update by no one reason than to update and something not working. I prefer to update only in case spotify has something new.. something new and tangible because the other upgrades were useless in new things.

Version 1.1.26.501 is NOT a testing version, it is the normal version.

The official Snap package of Spotify, is this version.

They just have not updated the http://repository.spotify.com/dists/stable/non-free/binary-amd64/Packages file.

what feature have the new version? Because the other ones was .. almost nothing ..

Maybe the current stable version will not be updated for the current debian release. Since more and more out of date notifications come in, I think about switching to the suggested newer, "testing" version. Any objections?

The latest Spotify version provided at:

http://repository.spotify.com/pool/non-free/s/spotify-client

is the same provided in its snap package.

@johnprogrammer Perhaps the pinned comment is relevant to your concern.

Thank you for packaging Spotify for all users in AUR.

I searched and I found the latest Spotify version here:

http://repository.spotify.com/pool/non-free/s/spotify-client

Please update the AUR package.

Thank you a lot.

the deezer app is not official but works perfect. If someone want to give it a try and may be change to it, the link is here: https://aur.archlinux.org/packages/deezer/ The official app is supposed coming in the future but nobody knows. And... HAVE A TRAY icon built in!

May be you want to have this: https://community.spotify.com/t5/Live-Ideas/Desktop-Linux-Desktop-App-Minimize-to-taskbar-or-system-tray/idi-p/4804945

Vote and comment if you want. I hope this can help a little the topic

You can fix the GPG key issue by using:

curl -sS https://download.spotify.com/debian/pubkey_5E3C45D7B312C643.gpg | gpg --import -

https://aur.archlinux.org/packages/spotify-tray-git/

an unnoficial package that gives you the tray icon support.

@dabrianator You should rather follow Zignd's advice and add Spotify's signing key to your keyring instead of skipping the signature check entirely!

ekatonb's solution worked for me when I encountered

ERROR: One or more PGP signatures could not be verified! 

when running makepkg, skip the check

makepkg --skippgpcheck

Afterwards, I was able to get the tar.xz file and install it with sudo pacman -U *.xz

Not sure the dependency issue here.

Made spotify package and:

spotify: error while loading shared libraries: libnettle.so.8: cannot open shared object file: No such file or directory

Updated nettle package from nettle-3.5.1-2 to nettle-3.6-1 since nettle-3.6.1 provides libnettle.so=8-64 and libhogweed.so=6-64

then spotify: error while loading shared libraries: libnettle.so.7: cannot open shared object file: No such file or directory

oookay. Downgraded nettle back to version 3.5.1-2 aaaand spotify: error while loading shared libraries: libnettle.so.8: cannot open shared object file: No such file or directory

Latest update broke Spotify

spotify: error while loading shared libraries: libnettle.so.8: cannot open shared object file: No such file or directory

EDIT: Fixed by updating

I managed to fix the key issue doing so first:

curl -sS https://download.spotify.com/debian/pubkey.gpg | gpg --import -

and then I proceeded through the normal installation process inside the cloned local repository:

makepkg -i

Today I ran into

==> PGP keys need importing:
 -> 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90, required by: spotify
 -> 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45, required by: spotify

gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90

and

gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 4773BD5E130D1D45

adds the missing certificates

Keep getting the following error when trying to install the package with pacman:

sudo pacman -U spotify-1:1.1.10.546-4-x86_64.pkg.tar.xz

Gtk-Message: 11:55:39.613: Failed to load module "canberra-gtk-module"

Tried re-installing. Tried installing https://aur.archlinux.org/packages/lib32-libcanberra-gtk3/ manually

If you got this error: ==> ERROR: One or more PGP signatures could not be verified! you can skip gpg check: makepkg --skippgpcheck

Thank you so much {^-^}...

(\/)       

( ..)
c(")(")

gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 4773BD5E130D1D45

does the job.

I know lol but just figured i'd mention it anyway. New here. Anyway infact i did and it too gave me some error. It would appear the server isn't working. Just ran it again and it does give an error as below. Is there a way i can use a different server or something or skip the check maybe ? Or could I update the keys manually if i can get them someplace ? Anyway output is below :-

gpg --keyserver keyserver.ubuntu.com --recv-keys 4773BD5E130D1D45
gpg: keyserver receive failed: Server indicated a failure

Using different AUR helpers won't magically give you the needed PGP key. ;-) Have you tried the solution a few posts below your own (from @TheWaterOnFire)?

Been trying to install for the psat 4 days now. Spotify fails to install, tried with baph and yay. PGP keys are failing to verify. Servers indicating faliure. No clue what it all means but anyway below is the output of running the install. Any fix?

:: View/Edit the PKGBUILD for spotify? [Y/n] n
gpg: Note: trustdb not writable
:: Resolving missing pgp key for spotify: 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90
gpg: keyserver receive failed: Server indicated a failure
[sudo] password for v: 
gpg: keyserver receive failed: Server indicated a failure
==> ERROR: Remote key not fetched correctly from keyserver.
gpg: Note: trustdb not writable
:: Resolving missing pgp key for spotify: 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45
gpg: keyserver receive failed: Server indicated a failure
gpg: keyserver receive failed: Server indicated a failure
==> ERROR: Remote key not fetched correctly from keyserver.
==> Making package: spotify 1:1.1.10.546-4 (Sat 11 Apr 2020 22:03:27 IST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found spotify.protocol
  -> Found LICENSE
  -> Downloading spotify-1.1.10.546-Release...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  2434  100  2434    0     0   6100      0 --:--:-- --:--:-- --:--:--  6085
  -> Downloading spotify-1.1.10.546-Release.sig...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   833  100   833    0     0   2414      0 --:--:-- --:--:-- --:--:--  2414
  -> Downloading spotify-1.1.10.546-x86_64.deb...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  109M  100  109M    0     0  2405k      0  0:00:46  0:00:46 --:--:-- 1885k
  -> Downloading spotify-1.1.10.546-x86_64-Packages...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  4197  100  4197    0     0  11561      0 --:--:-- --:--:-- --:--:-- 11561
==> Validating source files with sha512sums...
    spotify.protocol ... Passed
    LICENSE ... Passed
    spotify-1.1.10.546-Release ... Skipped
    spotify-1.1.10.546-Release.sig ... Skipped
==> Validating source_x86_64 files with sha512sums...
    spotify-1.1.10.546-x86_64.deb ... Passed
    spotify-1.1.10.546-x86_64-Packages ... Passed
==> Verifying source file signatures with gpg...
    spotify-1.1.10.546-Release ... FAILED (unknown public key 4773BD5E130D1D45)
==> ERROR: One or more PGP signatures could not be verified!
:: Exited spotify build early

@florianstascheck

It may be an optional dependency of spotify but that doesn't mean an issue with it is the fault of this package.

You need to remove ffmpeg-compat-57 before doing the system upgrade, then reinstall it, so that it is rebuilt against the new version of libx265.

See comments: https://aur.archlinux.org/packages/ffmpeg-compat-57

There was a problem with the ffmpeg-compat-57 dependency of spotify:

:: installing x265 (3.3-1) breaks dependency 'libx265.so=179-64' required by ffmpeg-compat-57 :: spotify optionally requires ffmpeg-compat-57: Adds support for playback of local files

Second time I tried installing on a fresh arch installation, fails while creating the package.

/usr/bin/makepkg: line 723: /.../spotify/spotify-1:1.1.10.546-4-x86_64.pkg.tar.xz: Invalid argument
bsdtar: Write error
==> ERROR: Failed to create package file.

Other AUR packages are fine, ideas?

My Spotify is unable to show liked/favorite songs anymore. It just says "Your favorite songs will appear here...". Anyone got a solution?

edit: I went with the nuclear option. Removed everything spotify in ~/.config and ~/.cache. Then reinstalled the package. It behaves normally now.

Looks like there's an update to the Apt public keys...

==> Verifying source file signatures with gpg...
    spotify-1.1.10.546-Release ... FAILED (unknown public key 4773BD5E130D1D45)

Appears there's an updated GPG key for this package: AskUbuntu Thread

So to resolve: gpg --keyserver keyserver.ubuntu.com --recv-keys 4773BD5E130D1D45

I also get a validation error while updating with yay: https://pastebin.com/fAxycLEP

No problems with pikaur though!

@d_fajardo this looks really strange. The files you named are not inside the PKGBUILD. You either did something completely wrong or your computer is potentially compromised, I dont know. A more detailed log would help, please use a pastebin service to post the log.

Couldn't update. I got this message updating:

==> Validating source files with sha512sums... font-symbola-13.00.zip ... FAILED LICENSE.pdf ... Passed ==> ERROR: One or more files did not pass the validity check!

Any solution?

@ShroudedNight where did you get this debian package from? I mean, how did you know about the newer version, maybe the gpg signatures are located somewhere else now?

@davidmogar thanks for the note. I do not know why AWhetter changed the dependencies (https://aur.archlinux.org/cgit/aur.git/commit/PKGBUILD?h=spotify&id=484bc2596d848327ce3ab4de1c2ac42cd815b127). I will take care of that.

I just installed it in a fresh Arch linux installation and it's missing, at least 2 dependencies: nss and at-spi2-atk.

Those dependencies are also reported by namcap and they provide libnss3.so, libXtst.so.6 and libatk-bridge-2.0.so.0, which are needed to run spotify.

Could you please add them?

--- PKGBUILD    2020-03-20 18:55:40.639218937 +0100
+++ PKGBUILD.modified   2020-03-20 18:59:51.502544477 +0100
@@ -14,10 +14,9 @@
 arch=('x86_64')
 license=('custom')
 url='https://www.spotify.com'
-depends=('alsa-lib>=1.0.14' 'bzip2' 'cairo' 'expat' 'fontconfig' 'freetype2'
-         'fribidi' 'graphite' 'gtk2' 'glib2' 'libpng' 'libsystemd'
-         'libx11' 'libxss' 'desktop-file-utils' 'nettle' 'openssl'
-         'p11-kit' 'pango' 'pcre' 'pixman')
+depends=('alsa-lib>=1.0.14' 'at-spi2-atk' 'bzip2' 'cairo' 'expat' 'desktop-file-utils'
+    'fontconfig' 'freetype2' 'fribidi' 'graphite' 'gtk2' 'glib2' 'libpng' 'libsystemd'
+         'libx11' 'libxss' 'nettle' 'nss' 'openssl' 'p11-kit' 'pango' 'pcre' 'pixman')
 depends_x86_64=('libcurl-gnutls')
 depends_i686=('libcurl-compat')
 optdepends=('ffmpeg-compat-57: Adds support for playback of local files'

Spotify isn't able to play my local files anymore. Earlier I once faced this issue, but it was fixed once I installed ffmpeg-compat-57, but this time it's installed and I still get the issue. It says Spotify can't play this right now. If you have the file on your computer you can import it.

If one is desperate to use the newer deb, as a stop-gap, overriding the check from *-packages allows the rest to move forward:

diff --git a/PKGBUILD b/PKGBUILD.modified
index 220686a..7c7b692 100644
--- a/PKGBUILD
+++ b/PKGBUILD.modified
@@ -4,10 +4,10 @@
 # Contributor: Eothred <yngve.levinsen@gmail.com>

 pkgname=spotify
-pkgver=1.1.10.546
+pkgver=1.1.26.501
 epoch=1
-_commit=ge08ef575
-_ver_x86_64=19
+_commit=gbe11e53b
+_ver_x86_64=15
 #_ver_i686=10
 pkgrel=3
 pkgdesc='A proprietary music streaming service'
@@ -41,7 +41,7 @@ sha512sums=('999abe46766a4101e27477f5c9f69394a4bb5c097e2e048ec2c6cb93dfa1743eb43
             '2e16f7c7b09e9ecefaa11ab38eb7a792c62ae6f33d95ab1ff46d68995316324d8c5287b0d9ce142d1cf15158e61f594e930260abb8155467af8bc25779960615'
             'SKIP'
             'SKIP')
-sha512sums_x86_64=('f004083eee00600a51e50d7dee03846293b5ccd6966786e91055564c7963917b9aaa917de41f299a0f5b7baecea5f466fb37722b8631743ff2ca15f43851f5f4'
+sha512sums_x86_64=('af9f1beafe0e4d2313326d1a55675550e8c3fcd5cd2dc0954127094c563048b98f74f669d99a10f0ef6e3b3405856bb9d6a2561644a434ab6bade9c812296963'
                    '39074e57abb9a647b4b27cc09bf91dd80a16589c8503b17061c23277b7718e778834bb79c168c771b9615d9e247f1ce9c5c597a10db905874a5d5c79f1109856')
 validpgpkeys=('931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90'
               '2EBF997C15BDA244B6EBF5D84773BD5E130D1D45') # Spotify <tux@spotify.com>
@@ -61,6 +61,7 @@ prepare() {

     echo "$(grep SHA512 ${pkgname}-${pkgver}-${CARCH}-Packages | head -n 1 | awk '{print $2}') ${pkgname}-${pkgver}-${CARCH}.deb" \
         > "${pkgname}-${pkgver}-${CARCH}.deb.sha512"
+    echo 'af9f1beafe0e4d2313326d1a55675550e8c3fcd5cd2dc0954127094c563048b98f74f669d99a10f0ef6e3b3405856bb9d6a2561644a434ab6bade9c812296963' "${pkgname}-${pkgver}-${CARCH}.deb" > "${pkgname}-${pkgver}-${CARCH}.deb.sha512"
     sha512sum -c "${pkgname}-${pkgver}-${CARCH}.deb.sha512"
 }

@Phhere Although the new DEB is available, it hasn't yet been released - the version in http://repository.spotify.com/dists/stable/non-free/binary-amd64/Packages is 1.1.10.546, the same version as this AUR package. At least as of when I posted this comment.

The new deb file is available on the debian repo https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.26.501.gbe11e53b-15_amd64.deb

The snap from spotify has a higher version than this AUR package. But the apt repository that Spotify provides has the same version as that from this AUR package. Unless someone creates an AUR package from the snap sources, or Spotify updates the debian package, this package cannot be updated.

Is the GPG key 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90 required?

I don't have it imported and the package builds correctly...

Getting the below error while trying to build

error: error while reading package /home/mukund/.cache/yay/spotify/spotify-1:1.1.10.546-3-x86_64.pkg.tar.xz: Truncated input file (needed 143018496 bytes, only 0 available)
error: '/home/mukund/.cache/yay/spotify/spotify-1:1.1.10.546-3-x86_64.pkg.tar.xz': libarchive error

I tried deleting the cache and trying again, at which point it got to Compressing package... and then froze. During the waiting period, my CPU temp shot up by 10 degrees C.

==> Sources are ready.
==> Making package: spotify 1:1.1.10.546-3 (Thu 20 Feb 2020 06:43:32 PM EST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Entering fakeroot environment...
==> Starting package()...
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "spotify"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Generating .MTREE file...
  -> Compressing package...

I had key verification problem and below line did the job curl -sS https://download.spotify.com/debian/pubkey.gpg| gpg --import

Just do the following then rebuild to fetch the key.

gpg --recv-keys 4773BD5E130D1D45

To manually add the gpg key, I had to run gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90 , then install continued as expected.

@E3LDDfrK I had the same issue. Rebuilding ffmpeg-compat-57 also installed yasm. Now Spotify plays local files again, thanks!

@Spheerys I think they key is supposed to be added manually to your user's keyring, See the Wiki

The curl command also works for me. But I have one question : why THIS package has issue with it's gpg key ?

curl -sS <https://download.spotify.com/debian/pubkey.gpg>| gpg --import

worked for me as well.

@Lorus Look at @nuc's comment below: curl -sS <https://download.spotify.com/debian/pubkey.gpg>| gpg --import

Im Getting
spotify-1.1.10.546-Release ... FAILED (unknown public key 4773BD5E130D1D45)

@teddyfrozevelt Same here, installed spotify on a fresh archlinux install and got:

spotify: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory

I'm having this issue 17:49:46.831 I [network_controller.cpp:93 ] Enabling AP network 17:49:46.831 I [network_controller.cpp:81 ] Connection type is initially 17:49:46.831 I [connectivity_manager.cpp:248 ] Connectivity rules changed fr 1 (roaming: 1), sync over wifi: 1, sync over cellular: 0 17:49:46.831 I [connectivity_manager.cpp:111 ] Scheduling emission of signal 17:49:46.831 I [connectivity_manager.cpp:102 ] Emitting signal. 17:49:52.562 I [local_authenticator.cpp:421 ] Skipping offline login: no such user 17:49:57.616 I [dns.cpp:60 ] Resolved apresolve.spotify.com to 34.98.74.57 17:49:57.870 I [request_accounting.cpp:416 ] High request latency: http://apresolve.spotify.com/ took 5304 ms 17:49:57.870 I [ap_connection_impl.cpp:505 ] Connecting to AP guc3-accesspoint-a-h259.ap.spotify.com:4070 17:50:02.876 E [ap_connection_impl.cpp:438 ] AP Socket Error: Timeout reached (20000) 17:50:02.876 E [ap_handler_impl.cpp:822 ] Connection error: ap_tcp_socket_timeout 17:50:02.876 I [ap_connection_impl.cpp:505 ] Connecting to AP guc3-accesspoint-a-ccjd.ap.spotify.com:443 17:50:02.926 I [dns.cpp:60 ] Resolved guc3-accesspoint-a-h259.ap.spotify.com to 104.154.126.83 17:50:07.925 E [ap_connection_impl.cpp:438 ] AP Socket Error: Timeout reached (20000) 17:50:07.926 E [ap_handler_impl.cpp:822 ] Connection error: ap_tcp_socket_timeout 17:50:07.926 I [ap_connection_impl.cpp:505 ] Connecting to AP guc3-accesspoint-a-z3z8.ap.spotify.com:80 17:50:07.983 I [dns.cpp:60 ] Resolved guc3-accesspoint-a-ccjd.ap.spotify.com to 104.154.127.158 17:50:12.931 E [ap_connection_impl.cpp:438 ] AP Socket Error: Timeout reached (20000) 17:50:12.931 E [ap_handler_impl.cpp:822 ] Connection error: ap_tcp_socket_timeout 17:50:12.931 I [ap_connection_impl.cpp:505 ] Connecting to AP guc3-accesspoint-a-xj2x.ap.spotify.com:4070 17:50:13.042 I [dns.cpp:60 ] Resolved guc3-accesspoint-a-z3z8.ap.spotify.com to 104.154.127.33 17:50:17.937 E [ap_connection_impl.cpp:438 ] AP Socket Error: Timeout reached (20000) 17:50:17.937 E [ap_handler_impl.cpp:822 ] Connection error: ap_tcp_socket_timeout 17:50:17.937 I [ap_connection_impl.cpp:505 ] Connecting to AP guc3-accesspoint-a-hqmf.ap.spotify.com:443 17:50:18.100 I [dns.cpp:60 ] Resolved guc3-accesspoint-a-xj2x.ap.spotify.com to 104.154.126.242 17:50:22.943 E [ap_connection_impl.cpp:438 ] AP Socket Error: Timeout reached (20000) 17:50:22.943 E [ap_handler_impl.cpp:822 ] Connection error: ap_tcp_socket_timeout 17:50:22.943 I [ap_connection_impl.cpp:505 ] Connecting to AP guc3-accesspoint-a-gtf5.ap.spotify.com:80 17:50:23.158 I [dns.cpp:60 ] Resolved guc3-accesspoint-a-hqmf.ap.spotify.com to 104.154.126.43 17:50:27.948 E [ap_connection_impl.cpp:438 ] AP Socket Error: Timeout reached (20000) 17:50:27.948 E [ap_handler_impl.cpp:822 ] Connection error: ap_tcp_socket_timeout 17:50:27.948 I [ap_connection_impl.cpp:505 ] Connecting to AP gae2-accesspoint-a-tn3c.ap.spotify.com:4070 17:50:28.214 I [dns.cpp:60 ] Resolved guc3-accesspoint-a-gtf5.ap.spotify.com to 35.190.245.187 17:50:32.954 E [ap_connection_impl.cpp:438 ] AP Socket Error: Timeout reached (20000) 17:50:32.954 E [ap_handler_impl.cpp:822 ] Connection error: ap_tcp_socket_timeout 17:50:32.954 I [ap_connection_impl.cpp:505 ] Connecting to AP gae2-accesspoint-a-gkqh.ap.spotify.com:443 17:50:33.272 I [dns.cpp:60 ] Resolved gae2-accesspoint-a-tn3c.ap.spotify.com to 104.199.240.132 17:50:37.959 E [ap_connection_impl.cpp:438 ] AP Socket Error: Timeout reached (20000) 17:50:37.960 E [ap_handler_impl.cpp:822 ] Connection error: ap_tcp_socket_timeout 17:50:37.960 I [ap_connection_impl.cpp:505 ] Connecting to AP gae2-accesspoint-a-ggdq.ap.spotify.com:80 17:50:38.328 I [dns.cpp:60 ] Resolved gae2-accesspoint-a-gkqh.ap.spotify.com to 104.199.240.30 17:50:42.965 E [ap_connection_impl.cpp:438 ] AP Socket Error: Timeout reached (20000) 17:50:42.965 E [ap_handler_impl.cpp:822 ] Connection error: ap_tcp_socket_timeout 17:50:43.393 I [dns.cpp:60 ] Resolved gae2-accesspoint-a-ggdq.ap.spotify.com to 104.199.241.132

My spotify just stopped being able to play local files today. Despite having ffmpeg-compat-57 installed. Rebuilding ffmpeg-compat-57 seems to solve the problem. Very weird.

Is the GPG key 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90 still required? The package builds correctly without it on my machine.

Nice! The only problem lays with the missing gpg key. But @sandman_pk solved it. Thanks, btw.

@jesusignacio It seems the new PKGBUILD already uses the HTTP link. Still it did not work work me.

curl -sS <https://download.spotify.com/debian/pubkey.gpg> | gpg --import

Fixed it however, thanks @sandman_pk!

Should libxss (https://www.archlinux.org/packages/extra/x86_64/libxss/) be listed as a run dependency? I got this error when trying to launch Spotify before installing it: spotify: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory

libxss also isn't in the dependency tree.

I got error: FAILED (unknown public key 4773BD5E130D1D45) ==> ERROR: One or more PGP signatures could not be verified!

Fix with: curl -sS https://download.spotify.com/debian/pubkey.gpg | gpg --import

And makepkg works just fine.

Meanwhile the error is fixed in a proper way, this is how I installed it: I just changed the URL in the PKBUILD in the line 36 (for amd64):

From https to http and from repository-origin.spotify.com/ to repository.spotify.com

And it worked for me. I hope this helps.

fuck You are right, Sorry, don't verify the package, recalculating

I found this, over there that reassures you :)

https://community.spotify.com/t5/Desktop-Linux/Spotify-install-not-working-due-to-TLS-shenaningans-snap-flatpak/td-p/4874544

@ijann I got an error: ==> Verifying source file signatures with gpg... spotify-1.1.10.546-Release ... FAILED (unknown public key 4773BD5E130D1D45) ==> ERROR: One or more PGP signatures could not be verified!

Edit: I used this command gpg --recv-key $KEYID now it's working!

I'll leave this over here

pgp not available, use at your own risk https://deb.pkgs.org/universal/spotify-amd64/spotify-client_1.1.10.546.ge08ef575-19_amd64.deb.html

Steps:

git clone https://aur.archlinux.org/spotify.git - this repository

cd spotify/ - enter the folder

download the file from the web indicated

save it in the cloned repository folder

rename the downloaded file to -> "spotify-1.1.10.546-x86_64.deb"

makepkg -cCifs

luck

still not possible to download files

@FoxNounours Same problem. Mine complained about ssl certificates. In the end I downloaded it manually using chromium. Just kept resuming until it's downloaded successfully. Then as the other comments like @lordchaos' or @phantar's said, you need to rename it.

The server hosting the package fails downloading the .deb for me as well. Unlike with most others switching to http://repository.spotify.com/ results in the same Error

==> ERROR: Failure while downloading http://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.10.546.ge08ef575-19_amd64.deb Aborting... :: Unable to build spotify - makepkg exited with code: 1

The server hosting the package fails downloading the .deb.

Solution (for now): Replace every instance of https://repository-origin.spotify.com/ with http://repository.spotify.com/ in the PKGBUILD.

Easy in gedit's ctrl + h, find, replace all function.

Even downloading the deb through browser fails half way with an unspecified "Failed - Network error" message. Anyway, that's how you can get the cleanest version of spotify on Arch.

Error message before my solution: ==> ERROR: Failure while downloading https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.10.546.ge08ef575-19_amd64.deb Aborting...

Edit: apparently it's already been suggested just as I advised, heh, well, at least it's at the top of the page so people can see it, and people seem to continue to complain about it not working even after it's been put out there.

If you use the url in the commentary:https://aur.archlinux.org/packages/spotify/#comment-721910 but with http it works

Just be patient. There's a solution a few posts below. I'd guess the maintainer is in their christmas/new year's holidays. Or just don't have time for it right now.

Having the same error as many others: ==> ERROR: Failure while downloading <https://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.10.546.ge08ef575-19_amd64.deb> Aborting...

Downloading manually allows you to install it though.

curl: (18) transfer closed with 86629054 bytes remaining to read ==> ERROR: Failure while downloading https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.10.546.ge08ef575-19_amd64.deb

curl: (18) transfer closed with 74801873 bytes remaining to read ==> ERROR: Failure while downloading <https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.10.546.ge08ef575-19_amd64.deb> Aborting... Error downloading sources: spotify

@AWhetter: During build I saw this: ==> Verifying source file signatures with gpg... spotify-1.1.10.546-Release ... Passed (WARNING: the key has expired.)

thought I'd let you know.

Thanks for keeping this maintained Merry Xmas and a Happy new year from the UK

Getting the error:

Failure while downloading https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.10.546.ge08ef575-19_amd64.deb

i think, as bulletmark suggested (https://aur.archlinux.org/packages/spotify/#comment-721910) you may need to change the host

Maintainer, as others have said here, change the source host from "https://repository-origin.spotify.com" to "http://repository.spotify.com". That second host is more generic and much more reliable. There is no need to use https for Arch package downloads as the source is check-summed anyhow.

The libxss package is missing in the dependencies

I'm getting the error "PKGBUILD contains CRLF characters and cannot be sourced." while updating this package. Anyone knows how to fix this?

One can also use this command to download it manually: wget -c https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.10.546.ge08ef575-19_amd64.deb -O spotify-1.1.10.546-x86_64.deb

For people having trouble downloading the .deb, try a downloader like "axel" that will auto-retry/resume. Spotify's repo seems to be having issues, so this will keep resuming until it succeeds. Then rename the downloaded .deb to match the PKGBUILD's naming convention. For example (using current version at time of writing):

mv spotify-client_1.1.10.546.ge08ef575-19_amd64.deb spotify-1.1.10.546-x86_64.deb

I'm getting: ERROR: Failure while downloading https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.10.546.ge08ef575-19_amd64.deb Aborting...

Package was inappropriately flagged out of date. If you want to install the latest version of this package on your system, edit your PKGBUILD (see the suggestions below). Otherwise file a bug.

fhenriquedev: Your suggestion to edit the PKGBUILD works perfectly. Thank you.

Is not possible to download https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.10.546.ge08ef575-19_amd64.deb for v1:1.1.10.546-2

I use yay to compile aur packages.

During the initialisation process I get this error:

==> PGP keys need importing: -> 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45, required by: spotify ==> Import? [Y/n] y :: Importing keys with gpg...... gpg: keyserver receive failed: Server indicated a failure ==> Error: Problem importing keys

Basically I don't manage to import that key. Any ideas what could be the cause?

1. download package spotify.tar.gz
2. unpack
3. into folder type makepkg -s --skippgpcheck --noconfirm
4. sudo pacman -U spotify-1:1.1.10.546-2-x86_64.pkg.tar.xz
5. sorted! ;)

@zangoku run gpg --recv-keys 4773BD5E130D1D45, it should help. That's not specific to this package, see https://forum.manjaro.org/t/aur-package-fails-to-verify-pgp-gpg-key-unknown-public-key-one-or-more-pgp-signatures-could-not-be-verified/42687

==> ERROR: Failure while downloading <https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.10.546.ge08ef575-19_amd64.deb> Aborting... Error downloading sources: spotify

@fhenriquedev thanks, this worked for me.

spotify-1.1.10.546-Release ... FAILED (unknown public key 4773BD5E130D1D45)
==> ERROR: One or more PGP signatures could not be verified!

for the ones who are experiencing the error, just edit the PKGBUILD file editing line 36: source_x86_64=("${pkgname}-${pkgver}-x86_64.deb::<https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_>${pkgver}.${_commit}-${_ver_x86_64}_amd64.deb"

to

source_x86_64=("${pkgname}-${pkgver}-x86_64.deb::<http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_>${pkgver}.${_commit}-${_ver_x86_64}_amd64.deb"

this will point the download to another repo that have the same .deb package, but unlike the original, this second is downloading normally

@pujianto, downloading it with aria and then renaming, works:

aria2c -x16 -s1000 https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.10.546.ge08ef575-19_amd64.deb -o spotify-1.1.10.546-x86_64.deb

I also encountered error while downloading the .deb. But i can still build by retrying multiple times, the partly downloaded file is resumed.

But i have been experiencing unresponsive UI when playing / skipping song, and it is still the same with this build, not sure what causing it.

I have 2 machines with different desktop, same problem. i3 at home and KDE at work.

*EDIT: Silly me. it is written in wiki to turn off notification (Show desktop notifications when the song changes) at settings to fix hang problem.

==> ERROR: Failure while downloading https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.10.546.ge08ef575-19_amd64.deb Aborting... Error downloading sources: spotify

=> Überprüfe Signaturen der Quell-Dateien mit gpg... spotify-1.1.10.546-Release ... FEHLGESCHLAGEN (Unbekannter öffentlicher Schlüssel 4773BD5E130D1D45) ==> FEHLER: Eine oder mehrere PGP-Signaturen konnten nicht überprüft werden! :: Unable to build spotify - makepkg exited with code: 1

Confirming what @slav describe

:: Parsing SRCINFO (1/1): spotify ==> Making package: spotify 1:1.1.10.546-2 (Thu 19 Dec 2019 10:17:17 AM EST) ==> Retrieving sources... -> Found spotify.protocol -> Found LICENSE -> Downloading spotify-1.1.10.546-Release... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 2434 100 2434 0 0 7726 0 --:--:-- --:--:-- --:--:-- 7726 -> Downloading spotify-1.1.10.546-Release.sig... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 833 100 833 0 0 4843 0 --:--:-- --:--:-- --:--:-- 4843 -> Downloading spotify-1.1.10.546-x86_64.deb... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 2 109M 2 3062k 0 0 500k 0 0:03:44 0:00:06 0:03:38 594k curl: (18) transfer closed with 111839611 bytes remaining to read ==> ERROR: Failure while downloading https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.10.546.ge08ef575-19_amd64.deb Aborting... Error downloading sources: spotify

I can confirm this behavior with this latest build. It always gives an error while downloading the .deb package.

Have afraid that something wrong with given link in PKGBUILD

curl: (18) transfer closed with 46537960 bytes remaining to read │==> ERROR: Failure while downloading https://repository-origin.spotify.com/pool/non-free/s/spotify-client/ │spotify-client_1.1.10.546.ge08ef575-19_amd64.deb │ Aborting... │The build failed.

There are currently no settings available for Window and Startup behavior. Are there any drawbacks, difficulties/incompatibilities that prevents these settings? I'm asking because I wanted to enable system tray minimization. I'm using Deepin DE. Thanks

Are you sure that this package requires gconf?

EDIT: It works without gconf.

@treeshateorcs

ffmpeg-compat-57 is need for local playback

Yes! Sorry I've been so slow to do this update. I'm aiming to have it done by the end of the week.

I'm having a lot of issues simply pausing and skipping songs. I'll click the pause/skip button and it'll push as if it's doing something, and then it doesn't happen for a while or it gets tired of me spamming it.

I can confirm that the package is working just fine without openssl1-1.0 and gconf.

why do some random local files can't be played? https://i.imgur.com/3ZvdmVe.png

Hey, gconf is no longer required by electron. openssl-1.0 neither. please remove

@WSDMatty I'm a user, I wanted to be convenience for friends who do not know. Thank you WSDMatty

OK, third try... please remove the obsolete gconf and openssl-1.0 dependencies

@dodafish Sure enough, the problem was on my end. I ran rm -fr on my source directory, cloned a fresh copy, ran makepkg -sri and got a successful build.

@hexadecagram if you really want to just upgrade spotify, clone the repository and run with makepkg.

git clone https://aur.archlinux.org/spotify.git
cd spotify
makepkg -sri

@leagto I have both 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90 and 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45 in my keyring. I still get "invalid public key" when trying to build spotify. I have tried setting trust levels for both keys at "I do not know", "marginally", and "fully" and still get the message.

You also must import key for 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90

I still get "invalid" (not "unknown") when using keyserver.ubuntu.com

By the way you can combine the download and the alternate keyserver into one command:

gpg --keyserver hkp://keyserver.ubuntu.com --recv-keys 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45

I have fix for error: FAILED (unknown public key 4773BD5E130D1D45).

You have to go to <http://keyserver.ubuntu.com>, search for "Spotify Public Repository Signing Key" and download key matching your error. Then import downloaded key using gpg --import <downloaded key>

Hope it helps

When trying to build this package, even after importing and trusting the key, I get:

spotify-1.1.10.546-Release ... FAILED (invalid public key 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45)

Note that it now says "invalid" not "unknown".

@serdarsaglam Created the package.

https://aur.archlinux.org/packages/spotify-tray-git/

Are you the creator of that application or just one you found?

Can you make Spotify tray icon AUR package? (Can be installed from source code)

Tested running smoothly: https://github.com/tsmetana/spotify-tray

It's not responding to commands some times. When I click on next button It's not change to the next song immediately & take 5 to 20 seconds some time. do any of you have the same experience ?

@stlaz Same with gconf. I already asked about it almost two months ago. Given the complete lack of feedback in the comment section, I wonder if maintainers are reading the comments at all.

Is there any specific reason this requires openssl-1.0? I tried to move this dependency to just 'openssl' and it seems to work fine.

I'm getting the error: "spotify-1.1.10.546-Release ... FAILED (unknown public key 4773BD5E130D1D45)" ==> ERROR: One or more PGP signatures could not be verified!

Using @modregod's suggestion to select a key worked.

spotify-1.1.10.546-Release ... HA FALLADO (clave pública desconocida 4773BD5E130D1D45

To solve:

gpg --keyserver hkp://keyserver.ubuntu.com --search-key 'Spotify Public Repository Signing Key'

And select the correct key.

@WSDMatty Thanks for the reply. I did a clean build and was able to get it to install.

Would that have been the cause? (i.e. Would it be possible that there were files leftover from a failed build that's causing the verification to fail?)

@thehungryturnip I could not reproduce your problem. This is probably something on your end. Make sure you're importing the proper key. The current Spotify public key is

2EBF997C15BDA244B6EBF5D84773BD5E130D1D45

Sometimes, using short keys can get you the wrong key. use

gpg --recv-keys 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45

That should install properly.

It seems like the key verification fails even after the import of the pgp key. Does this mean that the file isn't properly signed?

@Spheerys @olivercalder I can't import the key either, it claims alternately that there is no keyserver available, or that there is no data received from the keyserver... Which keyserver should I try to manually import the key from then?

please add at-spi2-atk as a dependency

I have zenity and ffmpeg-compat-57 installed alongside spotify-1:1.1.10.546-1, and playing local files used to work, but suddenly it isn't anymore (possibly due to an update or similar).

If I try to reproduce a local mp3, it displays "Spotify can't play this right now. If you have the file on your computer you can import it.", but it is already imported (thanks to zenity).

Reinstalling spotify and ffmpeg-compat-57 doesn't work, and executing spotify through the terminal doesn't print any errors when trying to play a local mp3.

Any tips on how to debug/solve this issue? Thanks!!

@carloshmm I cant visit the last website you have posted, they told me that I have not enough permissons to view this

@WSDMatty I've never enabled the testing repos but I'm having the exact same issue as obliqu1ty.

Looks like they deleted the idea from carloshmm's comment and upgraded the old request to an idea. Naturally they didn't bother to merge all the new votes over, and responded with a canned message about being over 500 votes.. which happened years ago. Edit: Oh, and didn't bother redirecting the deleted idea.

@Spheerys A more secure way of adding only the required key for this package, particularly for those not using an AUR helper, would be to add the specific key first. You can do this with:

gpg --recv-keys 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45

@treeshateorcs thanks ! But I had another issue with the PGP key for this package :

==> PGP keys need importing:
 -> 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45, required by: spotify
==> Import? [Y/n] 
:: Importing keys with gpg......
gpg: Unable to fetch GPG key from keyserver : not supported
==> Error: Problem importing keys

I had to install it by ignoring signature checking :

yay -S --mflags --skipinteg spotify

@Spheerys

clone this repo, install pacman-contrib, enter to the directory of this repo and run updpkgsums

I can't install the package because of this error :

spotify-1.1.10.546-Release ... FAILED
spotify-1.1.10.546-Release.sig ... Ignored

==> ERROR : One or several files are not valide !

Same for openssl-1.0, works fine without it

Can the gconf dependency be dropped? It's obsolete and spotify works fine without it

@modestoj Doing: "gpg --recv-keys 4773BD5E130D1D45" fixes the issue.

Can not install, failed at gpg step. The response was something like (not in english):

Verifying source code signature with gpg... spotify-1.1.10.546-Release ... FAILED (Unknown public key 4773BD5E130D1D45); ERROR: One or more PGP signatures could not be verified.

@WSDMatty SystemD seems to be the problem. Downgraded and it works fine now. Apps that autostarted were also slow so I will submit a bug report.

Edit: Maybe not, I downgraded then upgraded and now everything is fine which is strange. Really not sure on that one.

@obliqu1ty If you're on testing, try disabling testing and using pacman -syuu to roll back the testing packages that came in last night, reinstall, and see if it persists.

If it DOESN'T.. re-enable testing and add back the updates one by one until you isolate the one causing the problem and submit a bug report.

Sorry i couldn't be more help. You could also try submitting a bug to spotify themselves. This issue was seen a year ago, and solved in a new release. Perhaps they goofed and re-bugged the program.

@WSDMatty Same errors, cleared it's files in ~/.cache and ~/.config before reinstalling.

@obliqu1ty I am getting the same warnings, but spotify is functioning just fine.

If it's not functioning properly for you, you could try reinstalling?

I'm having trouble running this, woke up this morning and I get these errors when run from terminal. It is telling me I am offline when I have an active connection. I am on testing, fully updated.

spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by spotify)

/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)

/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)

@DonyorM @felipea.braga What is the actual problem makepkg is reporting? Is it saying invalid key, or key not trusted? Are you using an AUR helper? Have you cleared its cache?

Signature {problems,issues} is not a specific enough comment to get any useful help. I just cleared all package data and cache rebuilt this package without issue. If you provide some useful output, you'll receive a solution.

Also having signature issues on installation.

Unable to compile it, signature problems.

Thanks for fixing the build! Next time, please bump the pkgrel counter, I had to manually update the PKGBUILD in my helper(yay)'s cache and just found out after reading the comments here.

@Zemke That wasn't the problem. It didn't say missing key, it said invalid key. The PKGBUILD had the wrong signature in it. It's fixed now though. :)

@targodan you can simply import the key: gpg --recv-key <key>

https://wiki.archlinux.org/index.php/GnuPG#Use_a_keyserver

@AWhetter: That is great to hear, thank you!

I've fixed up the PKGBUILD. Sorry about the slowness of that.

I've fixed up the PKGBUILD. Sorry about the slowness of that.

I just created an account to tell thanks, It worked by adding the public key in the valid keys.

@NicoHood: Could you fix the line and signature keys please?

To get it work I had to extend the script of @dsasmind a bit:

git clone https://aur.archlinux.org/spotify.git

cd spotify

dos2unix PKGBUILD

makepkg -si --skipchecksums --skippgpcheck .

Seems like there is (still) something wrong with the gpg key. I get "spotify-1.1.10.546-Release ... FAILED (invalid public key 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45)"

@NicoHood

They just added this as a official idea! https://community.spotify.com/t5/Live-Ideas/Linux-Add-Spotify-to-the-official-Linux-repositories/idi-p/4813156

Please help spread the word!

PKGBUILD has Windows line endings (CRLF instead of LF), which results in:

==> ERROR: PKGBUILD contains CRLF characters and cannot be sourced.

@NicoHood: Could you change the line endings to LF, please? (e.g. with $dos2unix PKGBUILD)

It became an Idea guys, please upvote to the oblivion https://community.spotify.com/t5/Live-Ideas/Linux-Add-Spotify-to-the-official-Linux-repositories/idc-p/1695334

Included .sig file is signed with PGP key 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45 which is not the PGP key the PKGBUILD file is using (file seems to still be using old key, whilst listing it as old key as well).

The build of the package failed with error "ERROR: One or more PGP signatures could not be verified!"

I solved by adding the following key to the "validgpgkeys" field: 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45

Thanks for your job.

@sandsmark Thanks for the update. Just update the new fingerprint to validpgpkeys=(<fingerprint>) in PKGBUILD.

worked for me

for the time beeing as long its not fixed

git clone https://aur.archlinux.org/spotify.git
cd spotify
makepkg -ciS --skipchecksums .

The signature is made using another GPG key. Change the key in the PKGBUILD according to this diff:

diff --git a/PKGBUILD b/PKGBUILD
index d1783a9..8ed445a 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -43,7 +43,7 @@ sha512sums_x86_64=('f004083eee00600a51e50d7dee03846293b5ccd6966786e91055564c7963
                    '39074e57abb9a647b4b27cc09bf91dd80a16589c8503b17061c23277b7718e778834bb79c168c771b9615d9e247f1ce9c5c597a10db905874a5d5c79f1109856')
 # Old key: 0DF731E45CE24F27EEEB1450EFDC8610341D9410
 # Old key (17.12.2018): 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90
-validpgpkeys=('931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90') # Spotify <tux@spotify.com>
+validpgpkeys=('2EBF997C15BDA244B6EBF5D84773BD5E130D1D45') # Spotify <tux@spotify.com>

 # Spotify uses different names for the arch
 if [ "${CARCH}" = "i686" ]; then

You can add this key by running

gpg --recv-keys 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45

To verify yourself, instead of trusting random AUR users:

Download https://download.spotify.com/debian/pubkey.gpg from https://www.spotify.com/us/download/linux/, gpg --import pubkey.gpg, and then you can show the fingerprint with gpg --fingerprint and update the one in the PKGBUILD.

@Extremeadin Thanks for the updated info!

For anyone using Pamac GUI just edit the existing pkgbuild on-the-fly by viewing build files, replace the sigs with the ones in this guy's updated version and try installing again. All should work without a hitch.

Thanks killkrt, worked for me also.

If you are using yay you can skip integrity check (at this time) with:

yay -S --mflags --skipinteg spotify

If you are using yaourt to download AUR packages you can use option : --m-arg "--skippgpcheck --skipchecksum" to skip pgp and sha512sum checks, spotify should install now even though keys are not updated, it worked for me.

The old GPG key was pasted in instead of the updated one. You can use this PKGBUILD until the maintainer fixes it:

https://drive.google.com/open?id=1k6t4mytY5qMPmNAH4EFsXV8GAIgL9Xqd

even after importing GPG key, it fails at pub key validation.

spotify-1.1.10.546-Release ... FAILED (invalid public key 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45)

Installed the spotify-dev option until the sigs get updated. Seems fully functional.

Yes, @WhyNotHugo, but it would be best if the maintainer could update it.

@hbarcelos Just download the pkgbuild and update it locally.

Anyone able to fix the invalid signature error?

@NicoHood The source release files and gpg release key got updated. The new ones are:

1. spotify-1.1.10.546-Release: 86925c96c63161bfb488882e2afe663c1555fc904ba5b536097d82e474f7ac61071173214efc5dc0db54ac97cc801b7c531972556325eea454a59cb86e982254

2. GPG release key: 2EBF997C15BDA244B6EBF5D84773BD5E130D1D45

I also have a problem with installing version 1.1.10

    spotify.protocol ... Passed
    LICENSE ... Passed
    spotify-1.1.10.546-Release ... FAILED
    spotify-1.1.10.546-Release.sig ... Skipped
==> ERROR: One or more files did not pass the validity check!

Importing keys didn't work.

When installing the current version 1.1.10 I get the following error:

    spotify.protocol ... Passed
    LICENSE ... Passed
    spotify-1.1.10.546-Release ... FAILED
    spotify-1.1.10.546-Release.sig ... Skipped
==> ERROR: One or more files did not pass the validity check!

@orangecake I have the same issue on 1.0.94.262

@reikdas I am still on 1.1.5.153 and your observation makes me hesitant to actually upgrade. Did you also get this issue with 1.1.5.153 or did it just occur with 1.1.10.546?

My liked songs list doesn't sync with my account for some reason.

None of the typical solutions worked for me, including using a specific keyserver.

What worked for me is to temporarily disable setting SHA1 as a weak digest in the global gpg config by commenting the line like so:

#weak-digest SHA1

@matrs Hello!!! I used to have a similar problem before with the spotify's key and, if I recall correclty, the "ffmpeg2.8" key. Then I found a comment from a person called "sciant" somewhere between all the coments here and since I started using that person's method I had had no problem adding those two keys. Just add it this way and it may allow you to update spotify:

gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys A87FF9DF48BF1C90

Good Luck!! :D

When I do $ gpg --recv-key A87FF9DF48BF1C90 I get:

gpg: key A87FF9DF48BF1C90: 1 signature not checked due to a missing key
gpg: key A87FF9DF48BF1C90: public key "Spotify Public Repository Signing Key <tux@spotify.com>" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg:               imported: 1

and then When i try to update spotify I still get: One or more PGP signatures could not be verified!

Any suggestions?

You need to also import the spotify key to the keyring of your normal user as keycheck is performed with it using pacaur, yaourt, ... Hence do a

gpg --recv-key A87FF9DF48BF1C90

and you're good to go.

How to change playback device? help me. I found for windows but no for linux.

@kIERO - With those changes to this PKGBUILD, I get PGP errors.

    spotify-1.1.10.546-Release ... FAILED (unknown public key A87FF9DF48BF1C90)

I've done the whole dance of reinstalling pacman-keyring and refreshing the keys, but I can't get this key no matter what I try:

[shazbox] (~) >>> pacman-key --recv-key A87FF9DF48BF1C90
gpg: keyserver receive failed: Server indicated a failure
==> ERROR: Remote key not fetched correctly from keyserver.

I am, however, able to get a clean build with the PKGBUILD I shared earlier.

Hi ! While trying to install Spotify today, I got this error : "curl: (22) The requested URL returned error: 404"... at "https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.5.153.gf614956d-16_amd64.deb". this is due to the fact that the "spotify-client_1.1.5.153.gf614956d-16_amd64.deb" package is not available anymore and replaced by "spotify-client_1.1.10.546.ge08ef575-19_amd64.deb". Can you please update the link to the correct version so it will install ? Thanks for your help.

If you use the GNOME desktop environment you can open Software, search for Spotify and install it that way.

I changed the PKGBUILD to:

 pkgver=1.1.10.546
 _anotherpkgver=ge08ef575
 _amd64_pkgrel=19

It works... Please update de package.

Quite possibly. I think I may have just used an old one I had laying around as my basis.

If anyone else is interested, feel free to fork the current and make the appropriate changes, using my build as reference. :)

Otherwise, I'll take a stab at it after I get some sleep.

@skudd interesting the PKGBUILD from you is different to mine. Maybe an older version of the PKGBUILD on your end?

@rezzect - Apparently my hastebin.com link from earlier expired. Here's a pastebin.com link: https://pastebin.com/f1Ys3UhU

[tim@shazbox spotify]$ ls -l                                                                   
total 64                                                                                       
-rw-r--r-- 1 tim tim 51992 Jul 19 10:29 LICENSE 
-rw-r--r-- 1 tim tim  2526 Jul 19 11:46 PKGBUILD
-rw-r--r-- 1 tim tim    73 Jul 19 10:29 spotify 
-rwxr-xr-x 1 tim tim   166 Jul 19 10:29 spotify.protocol
[tim@shazbox spotify]$ makepkg -Cs
==> Making package: spotify 1.1.10.546-1 (Fri 19 Jul 2019 10:40:05 PM CDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found spotify
  -> Found spotify.protocol
  -> Found LICENSE
  -> Downloading spotify-client_1.1.10.546.ge08ef575-19_amd64.deb...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  109M  100  109M    0     0  21.6M      0  0:00:05  0:00:05 --:--:-- 23.8M
==> Validating source files with sha256sums...
    spotify ... Passed
    spotify.protocol ... Passed
    LICENSE ... Passed
==> Validating source_x86_64 files with sha256sums...
    spotify-client_1.1.10.546.ge08ef575-19_amd64.deb ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting spotify-client_1.1.10.546.ge08ef575-19_amd64.deb with bsdtar
==> Entering fakeroot environment...
==> Starting package()...
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "spotify"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: spotify 1.1.10.546-1 (Fri 19 Jul 2019 10:42:09 PM CDT)
[tim@shazbox spotify]$ ls -l
total 191200
-rw-r--r-- 1 tim tim     51992 Jul 19 10:29 LICENSE
drwxr-xr-x 3 tim tim      4096 Jul 19 22:40 pkg
-rw-r--r-- 1 tim tim      2526 Jul 19 22:42 PKGBUILD
-rw-r--r-- 1 tim tim        73 Jul 19 10:29 spotify
-rw-r--r-- 1 tim tim  80734212 Jul 19 22:42 spotify-1.1.10.546-1-x86_64.pkg.tar.xz
-rw-r--r-- 1 tim tim 114975574 Jul 19 22:40 spotify-client_1.1.10.546.ge08ef575-19_amd64.deb
-rwxr-xr-x 1 tim tim       166 Jul 19 10:29 spotify.protocol
drwxr-xr-x 2 tim tim      4096 Jul 19 22:40 src
[tim@shazbox spotify]$ 

@skudd what does your PKGBUILD look like here's mine https://pastebin.com/zstNShA2

@GwennShinguji - Try changing repository-origin to repository in the source_x86_64 variable declaration.

@rezzect - That's what I did with my PKGBUILD, though you're missing the . on _anotherpkgver

@GwennShinguji @skudd if you do the following you should have it running. yay -G spotify then cd spotify then with whatever editor of your choice (nano as an example) nano PKGBUILD and you are going to want to replace the following lines pkgver=1.1.5.153 to pkgver=1.1.10.546 then _commit=gf614956d to _commit=ge08ef575 then _ver_x86_64=16 to _ver_x86_64=19

once you do that save it then do makepkg -g >> PKGBUILD then finally do makepkg -si that should proceed to install with the right package and such.

Hmm, that's odd.

If you go to https://repository-origin.spotify.com/pool/non-free/s/spotify-client/ you will see that spotify-client_1.1.10.546.ge08ef575-19_amd64.deb is right there.

From my PKGBUILD:

 source_x86_64=("https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_${pkgver}${_anotherpkgver}-${_amd64_pkgrel}_amd64.deb")

And the relevant variable definitions:

 pkgver=1.1.10.546
 _anotherpkgver=.ge08ef575
 _amd64_pkgrel=19

trying to use yay and pamac (on Manjaro XFCE) both give me errors while trying to build Spotify. here's what it tells me:

curl: (22) The requested URL returned error: 404 ==> ERROR: Failure while downloading https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.5.153.gf614956d-16_amd64.deb Aborting...

is there a fix for this?

I have an updated PKGBUILD with the 1.1.10.546 client update. I'm pretty new to AUR contributions though, and the wiki doesn't seem very clear to me on how to submit it for merge.

I've dumped in on hastebin though, in case someone else with a bit more knowledge of the process wants to do the needful here.

https://www.hastebin.com/hoqawohica.makefile

As @gkrukar commented before, the Spotify repo has a different deb file now (new version).

https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.10.546.ge08ef575-19_amd64.deb

curl: (22) The requested URL returned error: 404 ==> ERROR: Failure while downloading https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.1.5.153.gf614956d-16_amd64.deb Aborting... :: Unable to build spotify - makepkg exited with code: 1

I have a strange error while trying to install spotify:

could not extract /opt/spotify/libcef.so (Lzma library error: No progress is possible)

If anyone receives this error

==> Verifying source file signatures with gpg...
    spotify-1.1.5.153-Release ... FAILED (unknown public key A87FF9DF48BF1C90)
==> ERROR: One or more PGP signatures could not be verified!

just run the following command.

gpg --recv-key A87FF9DF48BF1C90

Source

The out of date flag is wrong.

spotify tray is working, can the AUR package be?

https://github.com/tsmetana/spotify-tray

@Dante_Igashu Neither of the two apps work but I just installed spotifiy on another computer and it ,orked just fine, I am thinking my makepkg is doing something strange

@Traxys That's weird. I see there's some stuff gone in the spotify folder and for what you say it happened in two AUR app folders. You didn't answer my previous question, does spotify work? and now, does flutter work? or you are unable to use both apps, given there's some stuff missing. Have you tried reinstalling? if you did and there's still some stuff missing you could try removing the package like this:

sudo pacman -Rns spotify

this will remove the package, its configuration files and its dependencies, then you could try reinstalling and see what happens.

If the app works just fine even when there seems to be some stuff missing or if the problem remains, you could try asking in the "Forums" section, perhaps somebody knows what's happening. I made a quick search and found this:

https://bbs.archlinux.org/viewtopic.php?id=232451

Doesn't seems to be of any help, but seems to be something similar to your problem, so, you may not be the first with this issue and there might be someone who can help.

Good Luck! :D

@Dante_Igashu I'll output the result of ls /opt/spotify for version 1:1.0.98.78-2.1 and 1:1.1.5.153-1:

Apps cef_100_percent.pak cef_extensions.pak devtools_resources.pak icudtl.dat libEGL.so locales snapshot_blob.bin spotify.desktop v8_context_snapshot.bin apt-keys cef_200_percent.pak cef.pak icons libcef.so libGLESv2.so natives_blob.bin spotify swiftshader

After: Apps apt-keys cef_100_percent.pak cef_200_percent.pak cef_extensions.pak cef.pak devtools_resources.pak icons icudtl.dat libcef.so libEGL.so libGLESv2.so locales swiftshader

As you can see some important files disapeared. I have no binary named spotify in my path.

I could have a problem with some types of /opt packages flutter seems to have the same issue

@Traxys Hello! :D If you are referring to the executable file, I have one in /opt/spotify and a link in /bin and another link in /usr/bin for spotify. Yet I wonder why the question? :O Can you make use of spotify?

I do not have any binary named spotify installed in /opt/spotify or /usr/bin, am I the only one with this problem ?

@endre https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=spotify#n24

Wow, I'm truly amazed as this package left me with a spotify 'binary' full of 0x00's. :D

➜  ~ hexdump -C /opt/spotify/spotify
00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
044273b0  00 00 00 00 00 00 00 00                           |........|
044273b8
➜  ~ stat /opt/spotify/spotify
  File: /opt/spotify/spotify
  Size: 71463864    Blocks: 1          IO Block: 131072 regular file
Device: 16h/22d Inode: 275939      Links: 1
Access: (0755/-rwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2019-06-13 10:25:56.909021977 +0200
Modify: 2019-06-13 10:25:05.000000000 +0200
Change: 2019-06-13 10:25:51.138910003 +0200
➜  ~ pacman -Qi spotify
Name            : spotify
Version         : 1:1.1.5.153-1
Description     : A proprietary music streaming service
Architecture    : x86_64
URL             : https://www.spotify.com
Licenses        : custom
Groups          : None
Provides        : None
Depends On      : alsa-lib>=1.0.14  gconf  gtk2  glib2  nss  libsystemd  libxtst  libx11  libxss  desktop-file-utils  rtmpdump  openssl-1.0  libcurl-gnutls
Optional Deps   : ffmpeg-compat-57: Adds support for playback of local files
                  zenity: Adds support for importing local files [installed]
                  libnotify: Desktop notifications [installed]
Required By     : None
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 268.82 MiB
Packager        : Unknown Packager
Build Date      : Thu 13 Jun 2019 10:25:05 AM CEST
Install Date    : Thu 13 Jun 2019 10:25:51 AM CEST
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : None

Build details uploaded to: https://end.re/c2b195a49152d6554e78211ebe074d88a55c822404db01757b180ab324332974.txt

finally found the solution to graphical glitches without downgrading to 1.0.98:

https://community.spotify.com/t5/Desktop-Linux/Green-messy-glitch-on-the-app/m-p/4764184/highlight/true#M18377

spotify --disable-gpu (but cpu usage as shown in top raised about 2-3 times)

Everyone who has version 1.1.5.153 needs to be downgraded to 1.0.98.78-2.1. If you don't have a package cache, then download:

https://drive.google.com/file/d/1XzjXzF7Irtclg6D7Z854Xa_DrzAlQ7R2/view?usp=sharing

And downgrading with a sudo pacman -U spotify-1:1.0.98.78-2.1-x86_64.pkg.tar.xz

When building the latest version (1:1.1.5.153-1), my pc rebooted. Very scary. Avoid upgrading for now. Manjaro Xfce user here. Update: Reboot may be caused by something else.

@IdleGandalf Yep, welcome to the club. Downgrading seems to be the only solution for now.

I'm having graphic glitches all over the interface with 1.1.5.153 & mesa, can anyone confirm?

@alexkorpas: I had the same issue. After I changed password via Spotify's webpage it works again.

There you go: https://send.firefox.com/download/809910512d3b7ba1/#thEepSdFAOiPTPGYCLRB1Q

@arpanek Legend, thank you!

Am I the only one who can't log in? I have different errors every time I try, like the server is not available, error 7, firewall error, etc.

I tried to reinstall, delete ~/.config/spotify directory etc. I even tried snap package but also didn't work.

The same account on a different machine in the same network works without firewall settings. Any ideas?

There you go: https://send.firefox.com/download/809910512d3b7ba1/#thEepSdFAOiPTPGYCLRB1Q

@arpanek the tar.xz from your cache should be fine for them/me/anyone else who needs an older version

Downgrading with a sudo pacman -U ~/.cache/yay/spotify/spotify-1:1.0.98.78-2-x86_64.pkg.tar.xz worked.

What would be the alternative way to downgrade? I don't seem to have anything but the latest version in my yay cache directory.

edit: I checked out previous PKGBUILD, unfortunately it looks like older debs are unavailable at vendor's :-(

@therealfarfetchd Forgive my noob question, but will the tar.xz package that was saved in my cache be OK for you? It might have been built specifically for my machine, right?

@0003c9fe For discord, it's not only the startup screen, screen sharing is also affected.

And I'd appreciate it if someone could share an old version of the package, since I also haven't saved it.

Switching to the Flatpak version as an alternative to the Snap version: https://flathub.org/apps/details/com.spotify.Client

As Snap doesn't handle the cursor theme properly.

But it means I need GNOME Software for the auto updates. Oh well...

What happens to the latest version of spotify?

@glow8 I'm having the same issue, although I don't have an old version in my cache, and when I try the previous version I get "Failure while downloading https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.98.78.gb45d2a6b-10_amd64.deb"

Any ideas on where I can get an older version to downgrade to?

Edit: This also seems to be affecting other electron stuff like Discord (although only the startup window) as Freso said, although Discord started doing it around a week ago, spotify only started after the update.

New versions works as well for me as the previous did. (That is, it works perfectly until at some point it randomly freezes. This doesn’t seem to be specific to this program though, as it seems happens with all electron apps on my system: spotify, irccloud, discord, …)

Same here, very messy graphics

Downgrading with a sudo pacman -U ~/.cache/yay/spotify/spotify-1:1.0.98.78-2-x86_64.pkg.tar.xz worked.

@arpanek same for me. Tried disabling Compton, which didn't help. Rolling back for now.

Is it just me or is the latest version (1.1.5.153-1) unusable? I cannot do anything - whenever I move my mouse, the interface becomes messy.

@kallekj, perfect! Now working like a charm. It was my fault to not observe the lacking of LICENSE and spotify.protocol files. Sorry and thanks!

@jecogeo You get "differ in size from the source array" error when the number of items in the source=() doesn't match up with the number of items in the sha512sums=() arrays. In the sha512sums=() array, the first item is the sha512sum for spotify.protocol file, second is for LICENSE, third and fourth is for the Release and .sig file. Since there are no sha512 sums for Release and .sig file it skips checking these, hence the 'SKIP'.

Have you downloaded the spotify.protocol and LICENSE file from this AUR?

ERROR: Failure while downloading https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.98.78.gb45d2a6b-10_amd64.deb Aborting...

@kallekj, the package build uses sha512, not sha256, right? Do you think that's could be the problem with the error message saying "differ in size from the source array"?

@jecogeo I've just tried it again and it works fine for me, the SHA256sum of my PKGBUILD file should be 20961f6143d6552c1e27b5eb2e71e1640b6b4fc7d9f1609b2b814b6fcdbb129a

Here is the diff for 1.1.5.153:

diff --git a/PKGBUILD b/PKGBUILD
index 166b566..ae591c7 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -4,12 +4,12 @@
 # Contributor: Eothred <yngve.levinsen@gmail.com>

 pkgname=spotify
-pkgver=1.0.98.78
+pkgver=1.1.5.153
 epoch=1
-_commit=gb45d2a6b
-_ver_x86_64=10
-#_ver_i686=10
-pkgrel=2
+_commit=gf614956d
+_ver_x86_64=16
+#_ver_i686=16
+pkgrel=1
 pkgdesc='A proprietary music streaming service'
 arch=('x86_64')
 license=('custom')
@@ -39,8 +39,8 @@ sha512sums=('999abe46766a4101e27477f5c9f69394a4bb5c097e2e048ec2c6cb93dfa1743eb43
             '2e16f7c7b09e9ecefaa11ab38eb7a792c62ae6f33d95ab1ff46d68995316324d8c5287b0d9ce142d1cf15158e61f594e930260abb8155467af8bc25779960615'
             'SKIP'
             'SKIP')
-sha512sums_x86_64=('f20f2c998a205f189a19f332b2e738a0ec98a34520765c0e1d27d95d92f7c9c2f78da32f9edcc61146be87e8d8df7d3521d2e84b427cd25586b9fe6bec8d1602'
-                   '7f69b6a5b8647002be50210cf894b35fe0d2bc04e6b43321047e2229cd0ddae32c5684ea6befd9195c5fed730cfdaaecbdda14a1a8037c2be9e3d536d98a61a3')
+sha512sums_x86_64=('db354f161c35b5f1a2d633282fad8fccf565e0061e7d258012f28422d766630391d47d4dafe22448fb60f850bf4ccbfdf82443cf107e03727c077b2c62e524be'
+                   'a726ce2c61863429e5e2b8e624f94401bbb95ba54bbb266d23a15b0b7c2eb97ef2347b2446beeb0c222afab1dee6406edf719f228fe53e1aea2587eca2cdb8e1')
 # Old key: 0DF731E45CE24F27EEEB1450EFDC8610341D9410
 # Old key (17.12.2018): 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90
 validpgpkeys=('931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90') # Spotify <tux@spotify.com>

https://gist.github.com/teohhanhui/1388a5088e9035cd5193538853683082

@kallekj, I'm receiving an error message "ERROR: Integrity checks (sha512) differ in size from the source array." when using your PKGBUILD

Since this AUR package has been outdated for a while now, I decided to try installing the Snap package, and other than the Snap issue with not applying the correct cursor theme, it seems like the media keys (MPRIS) are not working either.

Conclusion: Switching back to the AUR package.

EDIT:

it seems like the media keys (MPRIS) are not working either

Might be a bug in the Spotify app itself :'(

I've updated the the PKGBUILD file to install the latest version of Spotify (1.1.5.153). First time i've done this so make sure to read through it thoroughly. Spotify is running great on my ManjaroI3 installation running Kernel 4.19.45-1.

The new PKGBUILD file can be downloaded from my github page: https://github.com/kallekj/ManjaroFiles

EDIT: You might have to add the PGP signature, gpg --recv-keys A87FF9DF48BF1C90 worked for me.

Please update PKGBUILD to the last spotify-client version (1.1.5.153) https://repository-origin.spotify.com/pool/non-free/s/spotify-client/

I just build this on a freshly installed system with 5.1 Kernel. The complete GUI interface of spotify was lagging to a point that it was unusable. In system monitor were 4 spotify processes running. When I started /opt/spotify/spotify from the terminal I got an error mentioning the terms sandbox and GPU. It is to be noted that my system indeed has 2 GPUs, a RX550 for the host and a RX570 for guest VMs, however I did not yet set up vfio and both GPUs were accessible to the host and drivers were loaded. So I followed the vfio procedure to load the vfio stub driver on boot for the RX570. Now there are only 3 spotify processes running. I still get the error mentioning sandbox and gpu again. Spotify works well now though. Should I report that upstream or is this specific to the build process?

spotify-1.0.98.78-Release ... FAILED (unknown public key A87FF9DF48BF1C90) Invalid public key

@beiranvand.karim the package is not out of date, as it uses the stable branch, not the testing version.

Hey. please update the repository

spotify-1.0.98.78-Release ... FAILED (unknown public key A87FF9DF48BF1C90)

@jecogeo I am not so in systemd yet but I believe it´s a user systemd, try to execute systemctl --user status dirmngr, it at least found a dead process for me.

@thilk0 I've tried to follow your steps, but it seems i don't have any dirmngr service at all. systemctl --restart drmngr returns: Failed to restart dirmngr.service: Unit dirmngr.service not found.

BTW, I'm frequently falling on GPG and checksum issues....

Importing the key fails due to missing configuration. I needed to

1. create the file /root/.gnupg/dirmngr with content

standard-resolver

1. Restart dirmngr
2. Import the key, or just installing the package

https://bbs.archlinux.org/viewtopic.php?id=220996

Had the same problem:

==> Verifying source file signatures with gpg... spotify-1.0.98.78-Release ... FAILED (unknown public key A87FF9DF48BF1C90) ==> ERROR: One or more PGP signatures could not be verified!

Solved it by importing the key into the keyring:

gpg --recv-key 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90

And got the key from Spotify's website:

https://www.spotify.com/ar/download/linux/

pacaur has been discontinued by it's author and is no longer supported. Please don't keep using it. If you need something similar. See yay.

In arch trying to update package using pacaur.

Verifying source file signatures with gpg... spotify-1.0.98.78-Release ... FAILED (unknown public key A87FF9DF48BF1C90) ==> ERROR: One or more PGP signatures could not be verified!

I've Updated the package, it should work again.

Whoever does not want to wait until this get fixed by the package maintainer can open up the buildfile in pamac and replace the hash-line:

   '235795bf313113b228dac4f6b2ec3a8d06c5c0d7a5cb12618407a389f8cdd83a94e2c6d0ca48989e18a5d90437f9c629d6d666181b6b8929f1a27c37249120a8'

with the new and correct hash:

'ecc7b2b6cb96466a7c7d10f4a64852f867aee91b971f9bb48b485db44fdb8d250e761236b10d4179a7bc64a780b20b5d92f7910064430329d4c3997e5cd9d9a8'

Same issue, on both my main Arch system, and a fresh install of Manjaro.

Same problem here, fresh install of Arch

Validating source files with sha512sums... spotify.protocol ... Passed LICENSE ... Passed spotify-1.0.98.78-Release ... FAILED spotify-1.0.98.78-Release.sig ... Skipped

Fresh Install of Antergos 19.4 Spotify outputs this:

==> Validating source files with sha512sums... spotify.protocol ... Passed LICENSE ... Passed spotify-1.0.98.78-Release ... FAILED spotify-1.0.98.78-Release.sig ... Skipped ==> ERROR: One or more files did not pass the validity check!

Same problem here. Fails to Validate: "spotify-1.0.98.78-Release ... FAILED".

Validating source files with sha512sums...
    spotify.protocol ... Passed
    LICENSE ... Passed
    spotify-1.0.98.78-Release ... FAILED
    spotify-1.0.98.78-Release.sig ... Skipped

This package is failed to validate

This package worked fine yesterday morning. But today it fails to validate. It looks like Spotify updated their end early this morning.

Validating source files with sha512sums...
    spotify.protocol ... Passed
    LICENSE ... Passed
    spotify-1.0.98.78-Release ... FAILED
    spotify-1.0.98.78-Release.sig ... Skipped

glow8, works here, but seems crossfade is now enabled despite it being disabled in the settings.

Settings drop-down menu not working for me. It does show up but clicking on the buttons (Settings/Account/...) does nothing

bbbenji's method to get over the key signature problem worked like a charm for me on version 1.0.98.78 A simple copy/paste on terminal was enough

gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90

spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)
[0331/220423.120494:ERROR:ssl_client_socket_impl.cc(1061)] handshake failed; returned -1, SSL error code 1, net_error -107
[1]    17705 segmentation fault (core dumped)  spotify

==> Starting prepare()... spotify-1.0.98.78-x86_64-Packages: OK spotify-1.0.98.78-x86_64.deb: OK ==> Sources are ready. :: failed to verify integrity or prepare spotify package

i make this:

go to "http://keyserver.ubuntu.com/" and search for "0x48bf1c90"

open "pub 4096R/48BF1C90 2018-05-23" and save content to file "key.pub"

run "gpg --import key.pub" and try install again :)

@tinmice The window simply freezes shortly after starting it; I can only press pause/play. I just control the songs from my phone.

Anyone having problems with it launching fullscreen without window decoration? You can't minimise, move, resize etc using keyboard shortcuts either.

I think there were some gnome updates last week or so and it hasn't work since then.

For anyone having issues with the key, try this:

gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90

@gothicknight It's described in manual, so there is no reason to mention this requirement here. By fetching GPG key, you are adding it to trusted signatures. In other words, by doing so, you say "I trust this signature."

You can read more here: https://wiki.archlinux.org/index.php/Makepkg#ERROR:_One_or_more_PGP_signatures_could_not_be_verified!

@dmaschine Just use gpg --recv-keys with a full key. "gpg --recv-keys 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90"

It should work with no issues.

I can't fetch the gpg key. I am getting an <unspecified source> error:

gpg: DBG: chan_3 <- OK Dirmngr 2.2.13 at your service gpg: DBG: connection to the dirmngr established gpg: DBG: chan_3 -> GETINFO version gpg: DBG: chan_3 <- D 2.2.13 gpg: DBG: chan_3 <- OK gpg: DBG: chan_3 -> KEYSERVER --clear hkps://hkps.pool.sks-keyservers.net gpg: DBG: chan_3 <- OK gpg: DBG: chan_3 -> KS_GET -- 0xA87FF9DF48BF1C90 gpg: DBG: chan_3 <- ERR 219 Server zeigt einen unbestimmten Fehler an <Quelle nicht angegeben> gpg: Empfangen vom Schlüsselserver fehlgeschlagen: Server zeigt einen unbestimmten Fehler an

I am using this command: gpg -vvv --debug-all --keyserver hkps://hkps.pool.sks-keyservers.net --recv-keys A87FF9DF48BF1C90

I already searched this error but I didn't find a solution. What's the problem here?

@NicoHood

I've marked because I was looking at the PKGBUILD and went to the download folder and saw this listed with a more recent date and version: spotify-client_1.1.0.237.g378f6f25-11_amd64.deb 14-Feb-2019 14:48 104760412

@ariejan Sorry but my knowledge on GPG is severely limited. Can't this update be done within the PKGBUILD? What are the implications of this?

@Anty0 There's no mention of this requirement to update manually, hence my post.

@psy0nic It isn't workaround, you are supposed to fetch GPG key manually.

I can confirm that @ariejan 's workaround fixed my PGP key failure that I've been having for a month or so.

@gothicknight You need to fetch Spotify's GPG key manually so makepkg can verify its authenticity.

gpg --keyserver hkps://hkps.pool.sks-keyservers.net --search-keys A87FF9DF48BF1C90

I have the same error as @gothicknight, the PGP key has expired.

@gothicknight The package is not out of date. Please check the latest version here:

http://repository.spotify.com/dists/stable/non-free/binary-amd64/Packages

The build failed on checksum:

[in portuguese] spotify-1.0.98.78-Release ... FALHOU (chave pública desconhecida A87FF9DF48BF1C90)

@Zeroedout Nope, runs fine for me. I just updated to all the latest packages, still runs fine.

I did run it from a terminal now, and get these warnings (but doesn't affect functionality at all):

$ spotify
/usr/share/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /usr/share/spotify/spotify)
/usr/share/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /usr/share/spotify/spotify)
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)
[0312/213917.145092:ERROR:edid_parser.cc(313)] invalid EDID: human unreadable char in name

I'm having the same problem as Ataraxy. Also, settings won't open, I wonder if it's related to this. I've made sure I'm up to date. @WhyNotHugo are you not having any issues?

My issue mysteriously fixed itself after reboot.

@Ataraxy: Are you sure all your other packages are up to date? I get a feeling it might be due to some outdated packages.

When starting, I see:

spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)

Is my configuration somehow different to everyone else's?

It's somewhat strange. It doesn't work with plughw.

I have .asoundrc:

defaults.pcm.dmix.rate 44100
defaults.pcm.rate_converter "speexrate_best"

ctl.equal {
        type equal;
}

pcm.plugequal {
        type equal;
#        slave.pcm "plug:dmix";
       slave.pcm "plughw:0,0";
}

pcm.!default { 
        type plug;
        slave.pcm plugequal;
}

Spotify plays when I switch from plughw to plug:dmix. Which is not desirable for various reasons (my sound card has dynamic sample rate that is automatically set to sample rate of file I play while dmix has static sample rate which is far from ideal).

Thing is that other applications work fine with plughw (I tested mpv and firefox through alsa) and so did Spotify until last Friday (last time I used it on this particular machine). I have no idea what broke during last week. I was barely using this computer (software is regularly upgraded).

@no4b I'm not sure that FFmpeg is even needed. It's not in a dependency list. Also, it works for me with 1:4.1.1-2.

Spotify stopped playing: [0308/093458.075650:ERROR:render_media_log.cc(30)] MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: no supported streams"} [0308/093458.075831:ERROR:render_media_log.cc(30)] MediaEvent: PIPELINE_ERROR DEMUXER_ERROR_NO_SUPPORTED_STREAM

I suppose that this is related to [2019-03-06 19:50] [ALPM] upgraded ffmpeg (1:4.1.1-1 -> 1:4.1.1-2) but I'm not sure.

Could you guys please stop flagging this package out of date, because it is not. We are now using the stable branch which you can find here: http://repository.spotify.com/dists/stable/non-free/binary-amd64/Packages

The latest version is Version: 1:1.0.98.78.gb45d2a6b-10

@antonrud Thanks! solve problem: gpg: reception from the keyserver failed:: Server indicated a failure

I'm using a color profile which messes the Google Chrome (and Spotify) colors up. This can be fixed (in Chrome) by going to chrome://flags/#force-color-profile and setting it to sRGB. How do I fix this in Spotify ??

If you have this error with yaourt:

==> Verifying source file signatures with gpg...
    spotify-1.0.98.78-Release ... FAILED (unknown public key A87FF9DF48BF1C90)
==> ERROR: One or more PGP signatures could not be verified!
==> ERROR: Makepkg was unable to build spotify.

like @eaburto said, just run: gpg --recv-keys A87FF9DF48BF1C90

and then try updating spotify again.

spotify is available as a snaps https://wiki.archlinux.org/index.php/Snap

Thanks for the note about the epoch, I've added it back in.

Also thanks for the help about the gpg signatures.

Someone also flagged the package out of date, which was not true. If the package is out of date, you must now look at the stable version of the debian package, not the development one: http://repository.spotify.com/dists/stable/non-free/binary-amd64/Packages

rafasc++

pushing the epoch addition and removal in one go (which might've happened, judging by the timestamps) is not valid either. if this was a local change you should've amended the commit instead of adding another one; you get to keep the epoch now - please re-add it.

@NicoHood If you bump epoch, you cannot bump it back. Every person that upgraded it to 1:1.0.98.78 will no longer get updates as they'll all be seen as downgrades because a missing epoch is equivalent of epoch=0.

"gpg --recv-keys 931FF8E79F0876134EDDBDCCA87FF9DF48BF1C90"

Try with the full key. I always add keys like this without any issues.

Thank you, @antonrud it works for me too!

gpg --keyserver hkp://keyserver.ubuntu.com:80 --receive-keys A87FF9DF48BF1C90

solved "Problem importing keys" for me.

@eaburto Yes, you are right. I completely missed sudo in @zilvervos answer.

Using sudo in this case is definitely a bad idea...

@Anty0 I dont know about the Server failure, but some comments here are trying to import the key using "sudo", but unless you are compiling the packages as root (please no), what is really needed is to import the key into the user keyring, i.e. the same command but without sudo.

I did "gpg --recv-keys A87FF9DF48BF1C90" as my user and recompile again and it all worked great.

Hope this help the people having troubles here

Hmm... Sorry, I'm starting to feel like I'll be unable to help you with all of those gpg problems... It's strange how inconsistent results we got here...

Maybe someone else will come along this thread and help all of you. (Maybe @zilvervos answer is the one, we are waiting for, unfortunately I can't confirm that...)

@Anty0 Thanks for your suggestion, but it did not help: sudo gpg --keyserver hkp://keyserver.ubuntu.com:80 --receive-keys A87FF9DF48BF1C90 gpg: keyserver receive failed: Server indicated a failure

In the end I imported the key via enigmail (gpg extension for Thunderbird) by copying the key via the clipboard http://keyserver.ubuntu.com/pks/lookup?op=get&search=0xA87FF9DF48BF1C90

@herve This doesn't seem like the good way to do so...

I would do that like this: gpg --keyserver hkp://keyserver.ubuntu.com:80 --receive-keys A87FF9DF48BF1C90

Edit: Yeah, that's possible. You have to call that twice to get key sometimes...

I downloaded the file from http://keyserver.ubuntu.com/pks/lookup?op=get&search=0xA87FF9DF48BF1C90 and added it to the Pacman keyring: "pacman-key --keyserver hkp://keyserver.ubuntu.com:80 -a spotify.sig" but I still get that signature error.

Edit: I just tried "gpg --receive-keys A87FF9DF48BF1C90" and it found the key instantly. Go figure.

After updating to spotify-1.0.98.78-2, I now get this error whenever I try to run it. /usr/local/bin/spotify: line 3: /usr/share/spotify/spotify: No such file or directory

@windy According to Spotify (https://www.spotify.com/cz/download/linux/) it can be found here: hkp://keyserver.ubuntu.com:80

I hadn't any problem to receive it usual way (I didn't have to add that server), but it may be possible, that I have added it some time ago...

On which keyserver has the key been uploaded to? I could not find it on any.

@zilvervos Did you try that at last twice?

This could by caused by missing server in gpg configuration or by communication error and because I didn't have this problem I suspect the second one to be the cause here.

In case, you forgot to do so during system setup, you can also try executing this: pacman-key --init

But I'm not sure, if this can help...

@Anty0 I get the following error

gpg --receive-keys A87FF9DF48BF1C90 gpg: keyserver receive failed: Server indicated a failure

@carmilso You have to add that key to trusted keys on your computer.

You can do it like this: gpg --recv-keys A87FF9DF48BF1C90

It throws an error now: spotify-1.0.98.78-Release ... FAILED (unknown public key A87FF9DF48BF1C90)

I have updated the package with the following changes: Switched to stable branch. Hopefully less bugs appear now. Dropped 32bit support (not supported by upstream for over a year now) Fixed ffmpeg dependency as suggested by the comment. Added GPG signature verification, https sources and sha512 hashes for better security while building. * Install to /opt which is the recommended location for 3rd party extracted debian packages. (see also teamspeak etc)

@NicoHood: I took the liberty of claiming spotify-dev, as I had my own packaging of spotify laying around, ready for commit. It's loosely based on both this package and github gists you added here in the past.

I'm open for communication to consolidate our packaging efforts of both spotify-dev and the stable spotify over time.

As desired by the recent request I will change this PKGBUILD to the spotify stable branch and add PGP signature verification. The epoch will increase, as this package is currently at a higher version number. The segfaults are possibly fixed then.

If desired, someone can create a copy of this package and name it spotify-dev, so you are still able to use the bleeding edge spotify package.

Why is the segmentation fault error not being fixed? Is it only affecting a small number of users?

Mine would only load a black window unless I installed appmenu-gtk-module and libcurl-gnutls

Please stick to stable releases from here on out or this will have to be renamed to spotify-devel.

The spotify-stable package was just deleted, so you may want to add its maintainer, NicoHood, as a co-maintainer.

Still getting segfaults on ffmpeg-compat-57.

% pacman -Q | egrep -i 'ffmpeg|zenity|spotify'
ffmpeg 1:4.1-3
ffmpeg-compat-57 3.4.2-2
spotify 1.0.98.78-1
zenity 3.30.0-1

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007fdcf383ea26 in malloc () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x7fdcb966b700 (LWP 18567))]

Replacing ffmpeg-compat-54 with ffmpeg-compat-57 fixed the segfaults for me.

Can confirm that Spotify crashes on boot. Same errors as @Grunzwanzling.

/usr/share/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /usr/share/spotify/spotify)

/usr/share/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /usr/share/spotify/spotify)

/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)

[0207/204010.712933:ERROR:sandbox_linux.cc(379)] InitializeSandbox() called with multiple threads in process gpu-process.

/usr/bin/spotify: line 2: 27520 Segmentation fault (core dumped) /usr/share/spotify/spotify "$@"

Please change the optional dependency ffmpeg-compat-54 to ffmpeg-compat-57.

When I try to start spotify, the following thing happens:

/usr/share/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no v equired by /usr/share/spotify/spotify) /usr/share/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no v equired by /usr/share/spotify/spotify) /proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version infor proc/self/exe) /usr/bin/spotify: line 2: 16915 Segmentation fault (core dumped) /usr/share/spotify/spotify "$@"

Can someone help me?

I manually built with version 1.0.98 and it fixed a bunch of issues with fetching playlists and also updated the UI to match the other non-Linux versions.

Spotify 1.0.98 is out: http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.98.78.gb45d2a6b-10_amd64.deb

Would it be possible to add an HiDPI option patch to the .desktop file : e.g. '--force-device-scale-factor=1.5' ?

Update the PKGBUILD to reflect update as follows. pkgver=1.0.96.181 _anotherpkgver=.gf6bc1b6b _amd64_pkgrel=12 pkgrel=1 sha256sums_x86_64=('2753635edf06280148a4f7886cc980ebef57d5f4c9d71ab25a782e95b2c8c34e')

Broke (presumably) with today's libidn2 update:

/usr/share/spotify/spotify: error while loading shared libraries: libidn2.so.0: cannot open shared object file: No such file or directory

It easily can be fixed by creating a symlink to libidn2.so:

mkdir -p /tmp/spotify && ln -s /usr/lib/libidn2.so /tmp/spotify/libidn2.so.0
LD_LIBRARY_PATH=/tmp/spotify spotify

EDIT: The libidn2 update also broke dig (from bind-tools), and presumably other packages too. So it probably isn't this package's fault.

I cannot input Chinese into Spotify.

I use plasma-kde and media integration worked for years (including media keys & notification), but since few weeks the integrations fails. Any idea why? libnotify 0.7.7-2 is installed. I tried a rebuild, but no success.

@676339784 are you on systemd-240?

Because there are some issues with DBUS there. Lots of programs and login managers have connectivity problems on it.

Getting this error on launch: g_dbus_connection_send_message: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

Though everything else works fine

@m3thodic that bug report doesn't actually do a whole lot for them. the compat packages always have been arch-specific hacks to try and get the new libraries in arch to work with the old abi's that spotify is written for. spotify as a product doesnt care because they link against probably whatever is shipped w/ ubuntu.

Confirmed as well that ffmpeg-compat-57 solves this.

Also submitted some gdb output to Spotify: https://community.spotify.com/t5/Desktop-Linux/Local-files-on-Arch-Linux-crashes-spotify/m-p/4635275#M17040

@AWhetter please update ffmpeg-compat-54 with ffmpeg-compat-57 when you get a minute, thanks!

I confirm, installing ffmpeg-compat-57 fixed it. Thank you @ajigsawnhalo

Spotify crashes when playing local files.

Installing ffmpeg-compat-57 rather than ffmpeg-compat-54 solved it for me.

I can't activate my input method to input Chinese/Japnese in Spotify. However, I can enable the input method in my DE.

Can confirm, Spotify crashes when attempting to play local files.

Currently, spotify crashes when trying to play local mp3 files. I already rebuilt ffmpeg-compat-54, did not fix the issue.

Spotify itself outputs:

[mp3 @ 0x7fe11529ae20] max_analyze_duration 5000000 reached at 5015510 microseconds
[mp3 @ 0x7fe115279540] Header missing

Analyzing the core dump does not reveal anything useful, as there are just countless threads, all polling or waiting for some event, except the following:

Stack trace of thread 16458:
    #0  0x00007fe0c6911cf1 av_buffer_unref (libavutil.so.52)
    #1  0x00007fe0c691932d av_frame_unref (libavutil.so.52)
    #2  0x00007fe0c691949a av_frame_free (libavutil.so.52)
    #3  0x0000000001bffda3 n/a (spotify)
    ...

A suggestion/request for the /usr/bin/spotify launcher scripts: please use 'exec' when launching /usr/share/spotify/spotify so that there's not a lingering shell process running.

Even better, how about only replace the /usr/bin/spotify launcher script for i686 builds and leave the symlink in place for x86_64.

Updated PKGBUILD for spotify-client_1.0.94.262.g3d5c231c-9_amd64.deb: https://pastebin.com/eadt8HAc

I tried to install today and got this error:

curl: (22) The requested URL returned error: 404 Not Found ==> ERROR: Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.92.390.g2ce5ec7d-18_amd64.deb Aborting...

Looking in the spotify repository, available versions are: spotify-client_1.0.72.117.g6bd7cc73-35_i386.deb, spotify-client_1.0.80.480.g51b03ac3-13_amd64.deb and spotify-client_1.0.94.262.g3d5c231c-9_amd64.deb.

Please update version 1.0.92.x to 1.0.94.x.

Change the PKGBUILD pkgver=1.0.92.390 _anotherpkgver=.g2ce5ec7d _amd64_pkgrel=18 sha256sums_x86_64=('039443c918f44f853ef293b5804481b503ae5a5ec63e2bc670e7aecfb6c84f80')

to

pkgver=1.0.94.262 _anotherpkgver=.g3d5c231c _amd64_pkgrel=9 sha256sums_x86_64=('92803D614DA2FD4802F801D85DA9CF786F34216BBFA6085D5791C3E8350B4F44')

@arquero You could be right, tbh I haven't used AWhetter's package. I used the stable as a base and manually changed the build to 1.0.92.390 (but had to ignore the pgp key as it's only supposed for the old version).

I don't really want to create an AUR package (too much first setup stuff). Maybe AWhetter is willing to update, if I send the changed stuff?

I have noticed an error that Spotify connect does not work if two linux PCs have the same home directory. If you are also annoyed by this bug or just want to help spotify take more care of the linux bugs, please comment and rate the following post in the spotify forum: https://community.spotify.com/t5/Desktop-Linux/spotify-connect-not-working-properly-on-linux/m-p/4596685#

@eq891 I've tried your solution but it didn't work for me : I got the same errors @Desdic describes. I've solved replacing "libcurl.so.3" with "libcurl-gnutls.so.4" and updating the sha256sum for the "spotify" file as seen in https://aur.archlinux.org/packages/spotify-stable/

@Desdic

Change...

!/bin/sh

export LD_PRELOAD=libcurl.so.3 /usr/share/spotify/spotify "$@"

into libcurl.so.4 in "spotify" file and manually update the sha256sums for this file in the PKGBUILD

Maybe I'll make an AUR-Package soon.

it seems that its linked against a old gnutls and curl

ERROR: ld.so: object 'libcurl.so.3' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
/usr/share/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /usr/share/spotify/spotify)
ERROR: ld.so: object 'libcurl.so.3' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
/usr/share/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /usr/share/spotify/spotify)
ERROR: ld.so: object 'libcurl.so.3' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)
[1116/081515.818004:ERROR:sandbox_linux.cc(379)] InitializeSandbox() called with multiple threads in process gpu-process.

After the last update (1.0.92.390-1) I can't change anymore the download folder for the songs. Everytime I reopen spotify it just change to home/radeox/.cache/spotify/Storage. With previous builds I could change it without problems? Any one has the same problem?

@AWhetter Thanks for your work on this AUR-package. NicoHood took your PKGBUILD as a base, but refined it pretty well. Could you please refine your PKGBUILD as well? (his build: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=spotify-stable )

Also I think the https source would be more secure. What do you think about it?

https://repository-origin.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.92.390.g2ce5ec7d-18_amd64.deb

https://repository-origin.spotify.com/dists/

Guys, I am running latest Manjaro XFCE and still have the problem with the black screen and I cannot find proper solution for it. On the first start after system reboot it is working fine, despite giving the libcurl-gnutls.so.4 error. But after closing the window once and re-opening spotify, every single time after the first start it only shows black screen. What can I do about it? I've even tried installing snapd and then spotify over snap but with the same result. I have libcurl-gnutls and libcurl-compat installed. I am not getting the libcurl.so.3 error.

Here's a link to the latest versions of spotify: http://repository-origin.spotify.com/pool/non-free/s/spotify-client/

Found this package to be broken again.

As of now this will help:

pkgver=1.0.92.390
_anotherpkgver=.g2ce5ec7d
_amd64_pkgrel=18
sha256sums_x86_64=('039443c918f44f853ef293b5804481b503ae5a5ec63e2bc670e7aecfb6c84f80')

Hi everyone. I am on holiday at the moment so I won't be able to update th package until Monday. If you are looking to install the package or get the latest version then please see the updated PKGBUILDs that people have kindly left in the comments.

Confirmed that the fix posted by cerikson works. Please update the PKGBUILD.

The package is 404ing again, change to to fix.

pkgver=1.0.89.313
_anotherpkgver=.g34a58dea
_amd64_pkgrel=5
sha256sums_x86_64='2d563ce0c8ed62e3ea37ee9a7d3f5fe6bb262f8773f556ff0a0a836706d2a8ab')

The radio from selected song functionality is broken in 1.0.88.353 for me, I downgraded to 1.0.88.480 and it became restored.

Spotify 1.0.88.353-1 working like a charm in Manjaro.

@warp yes you are right. However awhetter refused to include this fix, along with the GPG signature check. For an alternative package see https://aur.archlinux.org/packages/spotify-stable/

I don't think this is opensource right? Shouldn't it be installed to /opt?

Please merge this fork: https://github.com/hooddanielc/aur-spotify-fork

• Updated to version 1.0.88.353
• Old version returned a 404 and was replaced
• Fixes build using makepkg -s

Making the following changes to the PKGBUID fixes the 404 for Spotify source .deb

pkgver=1.0.88.353
_anotherpkgver=.g15c26ea1
_amd64_pkgrel=14
sha256sums_x86_64=('75cb915931e0b5d6480dde9d109f450e7e75bea036dda66332ce838286197c85')

Download for the spotify deb is 404'ing.

The download from http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.88.345.gc64d9bb3-2_amd64.deb is failing.

The provided link ( http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.88.345.gc64d9bb3-2_amd64.deb) returns 404.

I'm getting an error: https://pastebin.com/wMYkMw05
Updating these fields in the PKGBUILD helped: pkgver=1.0.88.353 _anotherpkgver=.g15c26ea1 _amd64_pkgrel=14 sha256sums_x86_64=('75cb915931e0b5d6480dde9d109f450e7e75bea036dda66332ce838286197c85')

I updated the PKGBUILD. It's working fine: https://github.com/keomaborges/aur-spotify-contrib/blob/master/PKGBUILD @nsirolli

I can't install the package, since sha256 validation fails on spotify-client_1.0.88.345.gc64d9bb3-2_amd64.deb. Any suggestions?

libcurl.so.3 doesn't exist in Arch:

ERROR: ld.so: object 'libcurl.so.3' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

'LD_PRELOAD' hack is no longer needed. Spotify is build against 'libcurl-gnutls.so.4' now. You can get rid of it.

Also, executing it like below will prevent leaving unnecessary shell process open:

#!/bin/sh
exec /usr/share/spotify/spotify "$@"

As @carmilso mentioned, I am completely unable to play local files. I just get the "This song is not available" error, regardless of what format I'm using.

@lordchaos: well if I remember correctly there is no full-time dev working on the linux version as linux has never really been officially supported, this is why there is now a half-backed webapp.

Is Spotify on Linux no longer supported? My mac client has version 1.0.85.257

@fsutil I have the same problem. I've just installed the latest version from AUR for first time (not an upgrade) and after I start the application I get the following errors in the console:

/usr/share/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /usr/share/spotify/spotify) /usr/share/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /usr/share/spotify/spotify) /proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe) [0622/123903.951302:ERROR:gpu_process_transport_factory.cc(1029)] Lost UI shared context. [0622/123904.003641:ERROR:service_manager_context.cc(252)] Attempting to run unsupported native service: /usr/share/spotify/content_renderer.service [0622/123909.589536:ERROR:web_plugin_impl.cc(38)] Widevine registration is not supported after context initialization

The application starts despite the errors - a window appears on screen but the windows is empty (dark blank) and now controls or login buttons are available. I've already allied the fix for libcurl.so.3 -> libcurl.so.4.5.0 but it seems I am facing another issue (just like you did) with libcurl-gnutls.so.4

Anyone faced this? Pleace, advice! Thanks!

Is someone else having problems when adding a source to listen local music? I press the button but it has no effects.

EDIT

After the last upgrading, i can open spotify, it works very well. But I have same output on command line.

@alexx

Thank you for your answer.

I've tried your solution. libcurl.so.3 issue has gone but problem is not solved.

$ spotify

/usr/share/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /usr/share/spotify/spotify)
/usr/share/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /usr/share/spotify/spotify)
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)

I have this in /usr/lib

$ ls -l libcurl*

libcurl-gnutls.so.3 -> libcurl-gnutls.so.4.5.0
libcurl-gnutls.so.4 -> libcurl-gnutls.so.4.5.0
libcurl-gnutls.so.4.0.0 -> libcurl-gnutls.so.4.5.0
libcurl-gnutls.so.4.1.0 -> libcurl-gnutls.so.4.5.0
libcurl-gnutls.so.4.2.0 -> libcurl-gnutls.so.4.5.0
libcurl-gnutls.so.4.3.0 -> libcurl-gnutls.so.4.5.0
libcurl-gnutls.so.4.4.0 -> libcurl-gnutls.so.4.5.0
libcurl-gnutls.so.4.5.0
libcurl.so -> libcurl.so.4.5.0
libcurl.so.3 -> libcurl.so.4.5.0
libcurl.so.4 -> libcurl.so.4.5.0
libcurl.so.4.5.0

@fsutil For "ERROR: ld.so: object 'libcurl.so.3' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored."

$ cd /usr/lib

$ ls -l libcur*

You have something like:

libcurl.so -> libcurl.so.4.5.0

libcurl.so.4 -> libcurl.so.4.5.0

libcurl.so.4.5.0

Then, create a symlink for libcurl.so.4.5.0 named libcurl.so.3:

ln -s libcurl.so.4.5.0 libcurl.so.3

or

ln -s /usr/lib/libcurl.so.4.5.0 /usr/lib/libcurl.so.3

About "libcurl-gnutls.so.4" error, I have no idea.

It shows a blank window. What should i do ?

ERROR: ld.so: object 'libcurl.so.3' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
/usr/share/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /usr/share/spotify/spotify)
ERROR: ld.so: object 'libcurl.so.3' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
/usr/share/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /usr/share/spotify/spotify)
ERROR: ld.so: object 'libcurl.so.3' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)

@emvigo, the AUR is used by other Arch based distros, e.g. ArchLinux32 at https://archlinux32.org/.

Hi! First, thanks for packaging this! :) Just a question: Do we really need all that code for i686, considering that Arch doesn't support 32 bits architectures any longer? Cheers!

While trying to update to the build for the very latest version, I'm getting the below FYI

==> Finished making: spotify 1.0.80.480-1 (Fri 01 Jun 2018 09:15:27 AM CEST)
==> Installing package spotify with pacman -U...
[sudo] password for anavarre: 
==> WARNING: Failed to install built package(s).
==> ERROR: An unknown error has occurred. Exiting...

newest version as for 31.05.18

pkgver=1.0.80.480
_anotherpkgver=.g51b03ac3
_amd64_pkgrel=13

sha256sums_x86_64=('e32f4816ae79dbfa0c14086e76df3bc83d526402aac1dbba534127fc00fe50ea')

The upx option was removed from makepkg and it's causing this package to fail building. I think removing upx from options should fix the issue

@rerep The one in the music controls on the bottom of the program is working fine here. Not sure where the other one you mentioned should be though, since I'm new to Spotify.

Shuffle seems to have stopped working. It's grayed out in music controls and the green shuffle button is gone.

Apologies for the really minor silly nitpick but could the last line of the shell script wrapper be changed to exec /usr/share/spotify/spotify "$@" so as to not keep an extra shell running?

Works after reboot.

I'm running 1.0.79.223-1 and got

ERROR: ld.so: object 'libcurl.so.3' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
/usr/share/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /usr/share/spotify/spotify)
ERROR: ld.so: object 'libcurl.so.3' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
/usr/share/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /usr/share/spotify/spotify)
ERROR: ld.so: object 'libcurl.so.3' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)
[0429/211435.872070:ERROR:service_manager_context.cc(252)] Attempting to run unsupported native service: /usr/share/spotify/content_renderer.service

Along with empty black Spotify window. Installing libcurl-compat removed the lines that begin with ERROR: but retain the other lines and black window.

Just tested 1.0.79.223-1 from the updated AUR and it works for me again too. Thanks!

I confirm, it's fixed for me :). i've updated the PKGBUILD as I could not wait the aur update : https://pastebin.com/L6XbEbhx (x64 only)

I just saw an update to this not too long ago: https://community.spotify.com/t5/Desktop-Linux/1-0-77-core-dumps/m-p/4463033/highlight/true#M16352

The error handling bug has been fixed in 1.0.79

Anyone else having trouble playing local files? Got all the optional dependencies installed for local file playback.

this update also broke spotify for me with, exactly with the same consequences as burk3 explained. I didn't backup my built packages .. Lesson learned :)

@burk3 Yes, it's exactly the same for me. Until a little while ago I was able to run the Spotify app via snap, but even that doesn't work for me anymore ...

I'm seeing the same issue as @macfly, even after the upgrade. For me, the app opens its window and starts fading from black. After the fade is done (or almost done), it freezes, outputs the following lines on stderr, and dies:

terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
  what():  set_option: Cannot assign requested address
/usr/bin/spotify: line 3: 17677 Aborted                 (core dumped) /usr/share/spotify/spotify "$@"

The only other interesting info in stderr happens at the very beginning:

/usr/share/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /usr/share/spotify/spotify)
/usr/share/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /usr/share/spotify/spotify)
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)

Some googling seems to indicate that there is a SO versioning mismatch between the loading executable (spotify) and the SO trying to be loaded (libcurl-gnutls.so.4). I tried reinstalling both spotify and libcurl-gnutls to no avail. I also tried calling spotify directly (avoiding the now useless LD_PRELOAD since spotify moved off the libcurl-compat libraries (i.e. links against versioned SOs)) to no avail.

Is anyone else experiencing this? Any ideas on how I can fix this?

EDIT: I've also tried running via snap (like @hheld) to no avail.

@juloo: change the PKGEXT variable in /etc/makepkg.conf to something a different compression or remove the compression competently if you are building packages for local usage

PKGEXT='.pkg.tar'

See more in makepkg.conf(5) man pages (man makepkg.conf)

The final package is pretty huge (218MiB) and the compression step is slow

@fernandes, it's broken change package file to:

source_x86_64=("http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.77.338.g758ebd78-41_amd64.deb")

SHA256 is 0698d2dbda43f2866d2a6f6ed9816bf8022aa8cf67d0dba347f486410093e1a4

curl: (22) The requested URL returned error: 404 Not Found ==> ERROR: Fail download: http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.77.336.g0d3547d9-38_amd64.deb

Working PKGBUILD as of 01/04/18:

Maintainer: Ashley Whetter <(firstname) @ awhetter.co.uk>

Contributor: Eothred yngve.levinsen@gmail.com

pkgname=spotify pkgver=1.0.77.338 _i386_pkgver=1.0.72.117 _anotherpkgver=.g758ebd78 _i386_anotherpkgver=.g758ebd78 _amd64_pkgrel=41 _i386_pkgrel=35 pkgrel=2 pkgdesc="A proprietary music streaming service" arch=('x86_64' 'i686') license=('custom:"Copyright (c) 2006-2010 Spotify Ltd"') url="http://www.spotify.com" options=('!strip' '!upx')

source=('spotify' 'spotify.protocol' 'LICENSE') sha256sums=('989920e9360cadc1a8103b8c04acf0c87cb7911eb9a09dddb0cf4708d6249d34' 'af54f3b90cac46fa100b3f919a9225d10d847617d24aa9af3d832e7689f482c3' '4e8bea31ca27e16cac9c9dcd8f6ec27e1f82b45de86d6fee7a1e77e23f884b92') sha256sums_x86_64=('0698d2dbda43f2866d2a6f6ed9816bf8022aa8cf67d0dba347f486410093e1a4') sha256sums_i686=('f5ac29e8374901ce7401825d13471c03bcf6ec8106f8c210c710b0a8d7b22ca9')

source_x86_64=("http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_${pkgver}${_anotherpkgver}-${_amd64_pkgrel}_amd64.deb")

source_i686=("http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_${_i386_pkgver}${_i386_anotherpkgver}-${_i386_pkgrel}_i386.deb")

depends=("alsa-lib>=1.0.14" "gconf" "gtk2" "glib2" "nss" "libsystemd" "libxtst" "libx11" "libxss" "openssl-1.0" "desktop-file-utils" "rtmpdump") depends_x86_64=('libcurl-gnutls') depends_i686=('libcurl-compat') optdepends=('ffmpeg-compat-54: Adds support for playback of local files' 'zenity: Adds support for importing local files' 'libnotify: Desktop notifications' )

package() { cd "${srcdir}"

    tar -xzf data.tar.gz -C "${pkgdir}"

    install -D "${pkgdir}"/usr/share/spotify/spotify.desktop "${pkgdir}"/usr/share/applications/spotify.desktop
    install -D "${pkgdir}"/usr/share/spotify/icons/spotify-linux-512.png "${pkgdir}"/usr/share/pixmaps/spotify-client.png

    for size in 22 24 32 48 64 128 256 512; do
            install -D "${pkgdir}/usr/share/spotify/icons/spotify-linux-$size.png" \
                    "${pkgdir}/usr/share/icons/hicolor/${size}x${size}/apps/spotify.png"
    done

    chmod -R go-w "${pkgdir}"/usr

    # Bin Script
    rm "${pkgdir}"/usr/bin/spotify
    install -Dm755 "${srcdir}/spotify" "${pkgdir}/usr/bin/spotify"

    # Copy protocol file for KDE
    install -Dm644 "${srcdir}/spotify.protocol" "${pkgdir}/usr/share/kservices5/spotify.protocol"

    # License
    install -D -m644 LICENSE "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"

}

https://www.dropbox.com/s/d6dt35c2mhwy389/spotify-1.0.77.338-2-x86_64.pkg.tar.xz?dl=0

@AWhetter could you at least add somebody else as a co-maintainer, this breaks many AUR helpers.

Tmp PKGBUILD fix for x86_64 ver 1.0.77.338: https://bpaste.net/show/a241a3b530e7

As @diogobaeder mentioned, there's a typo in the urls, more specifically, there are "<" and ">" in source_x86_64 and source_i686 lines (Also in url but that doesn't affect the build). I removed them and I was able to update it.

A corrected PKGBUILD would be the following:

# Maintainer: Ashley Whetter <(firstname) @ awhetter.co.uk>
# Contributor: Eothred <yngve.levinsen@gmail.com>

pkgname=spotify
pkgver=1.0.77.338
_i386_pkgver=1.0.72.117
_anotherpkgver=.g758ebd78
_i386_anotherpkgver=.g6bd7cc73
_amd64_pkgrel=41
_i386_pkgrel=35
pkgrel=2
pkgdesc="A proprietary music streaming service"
arch=('x86_64' 'i686')
license=('custom:"Copyright (c) 2006-2010 Spotify Ltd"')
url="http://www.spotify.com"
options=('!strip' '!upx')

source=('spotify'
'spotify.protocol'
'LICENSE')
sha256sums=('989920e9360cadc1a8103b8c04acf0c87cb7911eb9a09dddb0cf4708d6249d34'
            'af54f3b90cac46fa100b3f919a9225d10d847617d24aa9af3d832e7689f482c3'
            '4e8bea31ca27e16cac9c9dcd8f6ec27e1f82b45de86d6fee7a1e77e23f884b92')
sha256sums_x86_64=('0698d2dbda43f2866d2a6f6ed9816bf8022aa8cf67d0dba347f486410093e1a4')
sha256sums_i686=('f5ac29e8374901ce7401825d13471c03bcf6ec8106f8c210c710b0a8d7b22ca9')

source_x86_64=("http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_${pkgver}${_anotherpkgver}-${_amd64_pkgrel}_amd64.deb")

source_i686=("http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_${_i386_pkgver}${_i386_anotherpkgver}-${_i386_pkgrel}_i386.deb")

depends=("alsa-lib>=1.0.14" "gconf" "gtk2" "glib2" "nss" "libsystemd" "libxtst" "libx11" "libxss" "openssl-1.0" "desktop-file-utils" "rtmpdump")
depends_x86_64=('libcurl-gnutls')
depends_i686=('libcurl-compat')
optdepends=('ffmpeg-compat-54: Adds support for playback of local files'
'zenity: Adds support for importing local files'
'libnotify: Desktop notifications'
)

package() {
    cd "${srcdir}"

    tar -xzf data.tar.gz -C "${pkgdir}"

    install -D "${pkgdir}"/usr/share/spotify/spotify.desktop "${pkgdir}"/usr/share/applications/spotify.desktop
    install -D "${pkgdir}"/usr/share/spotify/icons/spotify-linux-512.png "${pkgdir}"/usr/share/pixmaps/spotify-client.png

    for size in 22 24 32 48 64 128 256 512; do
        install -D "${pkgdir}/usr/share/spotify/icons/spotify-linux-$size.png" \
            "${pkgdir}/usr/share/icons/hicolor/${size}x${size}/apps/spotify.png"
    done

    chmod -R go-w "${pkgdir}"/usr

    # Bin Script
    rm "${pkgdir}"/usr/bin/spotify
    install -Dm755 "${srcdir}/spotify" "${pkgdir}/usr/bin/spotify"

    # Copy protocol file for KDE
    install -Dm644 "${srcdir}/spotify.protocol" "${pkgdir}/usr/share/kservices5/spotify.protocol"

    # License
    install -D -m644 LICENSE "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"
}

Thanks for the attention, AWhetter :-)

I couldn't run makepkg over the updated PKGBUILD because of some error regarding URLs (not sure why it's not recognizing it as a valid URL, even if I put the literal one), but I can certainly wait a few more days until we can have the updated package in AUR.

Here is the Link to the newest Package 'http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.77.338.g758ebd78-41_amd64.deb'.

Please update the PKGBUILD ...

Broken as of 29MAR2018 Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.77.336.g0d3547d9-38_amd64.deb

When i start spotify i've got that error:

ERROR: ld.so: object 'libcurl.so.3' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
/usr/share/spotify/spotify: error while loading shared libraries: libcurl-gnutls.so.4: cannot open shared object file: No such file or directory

Creating that link work around the issue:

ln -sv /usr/lib/libcurl-gnutls.so.4.0.0 /usr/lib/libcurl-gnutls.so.4

But after spotify is loading and crash with:

what():  set_option: Cannot assign requested address

did you already face that issue ?

Nuevo PKGBUILD / New PKGBUILD

# Maintainer: Ashley Whetter <(firstname) @ awhetter.co.uk>
# Contributor: Eothred <yngve.levinsen@gmail.com>

pkgname=spotify
pkgver=1.0.77.338
_i386_pkgver=1.0.72.117
_anotherpkgver=.g758ebd78
_i386_anotherpkgver=.g6bd7cc73
_amd64_pkgrel=41
_i386_pkgrel=35
pkgrel=2
pkgdesc="A proprietary music streaming service"
arch=('x86_64' 'i686')
license=('custom:"Copyright (c) 2006-2010 Spotify Ltd"')
url="<http://www.spotify.com>"
options=('!strip' '!upx')

source=('spotify'
'spotify.protocol'
'LICENSE')
sha256sums=('989920e9360cadc1a8103b8c04acf0c87cb7911eb9a09dddb0cf4708d6249d34'
            'af54f3b90cac46fa100b3f919a9225d10d847617d24aa9af3d832e7689f482c3'
            '4e8bea31ca27e16cac9c9dcd8f6ec27e1f82b45de86d6fee7a1e77e23f884b92')
sha256sums_x86_64=('0698d2dbda43f2866d2a6f6ed9816bf8022aa8cf67d0dba347f486410093e1a4')
sha256sums_i686=('f5ac29e8374901ce7401825d13471c03bcf6ec8106f8c210c710b0a8d7b22ca9')

source_x86_64=("<http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_>${pkgver}${_anotherpkgver}-${_amd64_pkgrel}_amd64.deb")

source_i686=("<http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_>${_i386_pkgver}${_i386_anotherpkgver}-${_i386_pkgrel}_i386.deb")

depends=("alsa-lib>=1.0.14" "gconf" "gtk2" "glib2" "nss" "libsystemd" "libxtst" "libx11" "libxss" "openssl-1.0" "desktop-file-utils" "rtmpdump")
depends_x86_64=('libcurl-gnutls')
depends_i686=('libcurl-compat')
optdepends=('ffmpeg-compat-54: Adds support for playback of local files'
'zenity: Adds support for importing local files'
'libnotify: Desktop notifications'
)

package() {
    cd "${srcdir}"

    tar -xzf data.tar.gz -C "${pkgdir}"

    install -D "${pkgdir}"/usr/share/spotify/spotify.desktop "${pkgdir}"/usr/share/applications/spotify.desktop
    install -D "${pkgdir}"/usr/share/spotify/icons/spotify-linux-512.png "${pkgdir}"/usr/share/pixmaps/spotify-client.png

    for size in 22 24 32 48 64 128 256 512; do
        install -D "${pkgdir}/usr/share/spotify/icons/spotify-linux-$size.png" \
            "${pkgdir}/usr/share/icons/hicolor/${size}x${size}/apps/spotify.png"
    done

    chmod -R go-w "${pkgdir}"/usr

    # Bin Script
    rm "${pkgdir}"/usr/bin/spotify
    install -Dm755 "${srcdir}/spotify" "${pkgdir}/usr/bin/spotify"

    # Copy protocol file for KDE
    install -Dm644 "${srcdir}/spotify.protocol" "${pkgdir}/usr/share/kservices5/spotify.protocol"

    # License
    install -D -m644 LICENSE "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"
}

There is no "http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.77.336.g0d3547d9-38_amd64.deb" package, I'd appreciate it if you could update the PKGBUILD.

The File 'http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.77.336.g0d3547d9-38_amd64.deb' don't exist ...

Please update the PKGBUILD. :)

Git Patch for the latest upgrade: https://pastebin.com/xuiQR2Yz

The upstream package seems to have been taken out. This is now the correct one: http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.77.338.g758ebd78-41_amd64.deb

To those who have problems installing amd64 version, edit PKGBUILD as follow:

To solve http 404 error:

pkgver=1.0.77.338
_anotherpkgver=.g758ebd78
_amd64_pkgrel=41

The new checksum from new version

sha256sums_x86_64=('0698d2dbda43f2866d2a6f6ed9816bf8022aa8cf67d0dba347f486410093e1a4')

Hi,

thanks for maintaining the pkg. I think the url is wrong?

curl: (22) The requested URL returned error: 404 Not Found ==> FEHLER: Fehler beim Download von http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.77.336.g0d3547d9-38_amd64.deb Breche ab...

While trying to download spotify-client_1.0.77.336.g0d3547d9-38_amd64.deb curl spits: curl: (22) The requested URL returned error: 404 Not Found

Even the given source here is down and throws a 404.

Please review the version number and consequently the filename because the curl request returns a 404 error. The correct filename is currently "spotify-client_1.0.77.338.g758ebd78-41_amd64.deb".

Please update the amd version to http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.77.338.g758ebd78-41_amd64.deb

From 8ca69193b18def969a98e64b3c51b55a7867d59a Mon Sep 17 00:00:00 2001
From: Agnaldo Junior <agnaldo.junior@itriad.org.br>
Date: Mon, 26 Mar 2018 15:14:06 -0400
Subject: [PATCH] Update to version 1.0.77.338

Signed-off-by: Agnaldo Junior <agnaldo.junior@itriad.org.br>
---
 PKGBUILD | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/PKGBUILD b/PKGBUILD
index bbb3364..5d325f0 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -2,11 +2,11 @@
 # Contributor: Eothred <yngve.levinsen@gmail.com>

 pkgname=spotify
-pkgver=1.0.77.336
+pkgver=1.0.77.338
 _i386_pkgver=1.0.72.117
-_anotherpkgver=.g0d3547d9
+_anotherpkgver=.g758ebd78
 _i386_anotherpkgver=.g6bd7cc73
-_amd64_pkgrel=38
+_amd64_pkgrel=41
 _i386_pkgrel=35
 pkgrel=2
 pkgdesc="A proprietary music streaming service"
@@ -21,7 +21,7 @@ source=('spotify'
 sha256sums=('989920e9360cadc1a8103b8c04acf0c87cb7911eb9a09dddb0cf4708d6249d34'
             'af54f3b90cac46fa100b3f919a9225d10d847617d24aa9af3d832e7689f482c3'
             '4e8bea31ca27e16cac9c9dcd8f6ec27e1f82b45de86d6fee7a1e77e23f884b92')
-sha256sums_x86_64=('65b56b378d2ce4193697048d1edee4e4a170ec92a5000693fcb8a23039980e9c')
+sha256sums_x86_64=('0698d2dbda43f2866d2a6f6ed9816bf8022aa8cf67d0dba347f486410093e1a4')
 sha256sums_i686=('f5ac29e8374901ce7401825d13471c03bcf6ec8106f8c210c710b0a8d7b22ca9')

 source_x86_64=("http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_${pkgver}${_anotherpkgver}-${_amd64_pkgrel}_amd64.deb")
-- 
2.16.3

/usr/bin/spotify --force-device-scale-factor=1.3

Spotify does not take the resolution of the screen into account. I have a 2560x1440 screen resolution and I'm using XFCE4 desktop environment with the xfwm4 window manager. I enabled the custom DPI settings and set them to 160. Everything looks fine except Spotify.

Does anyone face similar issues?

I was trying to install this package today and Spotify wasn't opening... I figure out that now we need to install a package called libcurl-gnutls, I suggest to put it as a dependence

Please replace the dependency on libcurl-compat with libcurl-gnutls in the PKGBUILD:

diff --git a/PKGBUILD b/PKGBUILD
index 003c583..31b3568 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -28,7 +28,7 @@ source_x86_64=("http://repository.spotify.com/pool/non-free/s/spotify-client/spo

 source_i686=("http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_${_i386_pkgver}${_i386_anotherpkgver}-${_i386_pkgrel}_i386.deb")

-depends=("alsa-lib>=1.0.14" "gconf" "gtk2" "glib2" "nss" "libsystemd" "libxtst" "libx11" "libxss" "openssl-1.0" "libcurl-compat" "desktop-file-utils" "rtmpdump")
+depends=("alsa-lib>=1.0.14" "gconf" "gtk2" "glib2" "nss" "libsystemd" "libxtst" "libx11" "libxss" "openssl-1.0" "libcurl-gnutls" "desktop-file-utils" "rtmpdump")
 optdepends=('ffmpeg-compat-54: Adds support for playback of local files'
 'zenity: Adds support for importing local files'
 'libnotify: Desktop notifications'

Since 1.0.77.336 spotify required libcurl-gnutls

@Aire-One thank you.

But to both you and anyone else having the same problem I guess the simplest solution is to just rebuild the AUR package so that it picks up the change in libpsl.

Once done then the problem is solved.

@lefterisjp, as I said, my solution for this issue is NOT a good solution. But here is what I did:

I checked the pacman packages cache (you could also use downgrade or manually download from the archives) for an older version of libpsl package.

I grabbed the /var/cache/pacman/pkg/libpsl-0.19.1-1-x86_64.pkg.tar.xz package (if I correctly recall) then uncompressed it in my /tmp and manually copied usr/lib/libpsl.so.5* to /usr/lib.

You will then have to manually manage the copied files when attempting an other upgrade operation. That's not the good solution to follow, but at least, you can easily make Spotify to work again, waiting for a better update.

Warning: completely downgrade the libpsl package (i.e. remove the new version of libpsl and reinstall an older) will broke your arch installation. Many packages need the new version, including pacman. So pacman -Syu will no longer works and you will need to manually reinstall the new version of libpsl with a pacman -U <local-file>.

After upgrading my packages spotify no longer works.

/usr/share/spotify/spotify: error while loading shared libraries: libpsl.so.5: cannot open shared object file: No such file or directory

@Aire-one how did you manage to solve this problem and have both versions of libpsl in your system?

@msudgh Had the same issue, something in my /etc/hosts was interfering with the login process, try clearing the file to log in.

After installing spotify, it doesnt show in the menu. I can run spotify with Alt+F2 --> spotify. But I cannot find it in the Mate menu.

What am I missing here?

After installation and launching, Spotify stuck on loading icon. Also, i reinstalled it. What's the problem?

Spotify is broken with the new version of libpsl from testing repo. Spotify need libpsl.so.5 (core/libpsl provide this version) where testing/libpsl update gives libpsl.so.6.

I managed to get both versions on my system but the way I did it is not viable. I think we should have something like for the openssl-1.0.

+1 & thanks for dropping ffmpeg0.10 for local, ffmpeg-compat-54 works just fine for me :)

curl: (22) The requested URL returned error: 404 Not Found

==> ERROR: Failure while downloading http://repository.spotify.com/pool/non-free/s/spotify-client/spotify-client_1.0.70.399.g5ffabd56-26_amd64.deb Aborting...

:: failed to verify spotify integrity

@windy thanks a lot for sharing this link! I will definitely add this to the spotify-stable package.

Sadly this mirror has no gpg signature, those have to be still pulled via http. Since its a digital signature it will still be okay though.

It would be better if this package would also check the GPG signatures for more security of the users. AWhetter just ignored my suggestions :/

There is also a HTTPS version of the repository, I would prefer using this one.

https://repository-origin.spotify.com/pool/

ffmpeg0.10 is orphan now and have issues with libvpx. I have replaced it with ffmpeg-compat-54 and everything work fine.

I think it is reasonable to replace ffmpeg0.10 (optional) – Adds support for playback of local files

to

ffmpeg-compat-54 (optional) – Adds support for playback of local files

If you are experiencing problems with the client while using a tiling window manager check the arch wiki spotify article, section Deadlock GUI Thread.

Due to the libcurl related issue I downgraded spotify to spotify-client_1.0.64.407.g9bd02c2d-26_amd64.deb. Is it the last working spotify version?

Spotify is still broken on the new version. Controls freeze after a while with music still playing. Not fixed until I restart the system.

Installation fails:

==> Validating source_x86_64 files with sha256sums... spotify-client_1.0.70.399.g5ffabd56-26_amd64.deb ... FAILED

Always get offline mode of spotify on my DDE, when i launched from console, i got this

/usr/share/spotify/spotify: /usr/lib/libcurl.so.3: no version information available (required by /usr/share/spotify/spotify)
/home/kowalski/.gtkrc-2.0:1: error: invalid keyword 'font_name', expected valid keyword - e.g. `style'
/usr/share/spotify/spotify: /usr/lib/libcurl.so.3: no version information available (required by /usr/share/spotify/spotify)
/proc/self/exe: /usr/lib/libcurl.so.3: no version information available (required by /proc/self/exe)

Anyway, thanks for your work.

For those interested, Spotify has released a "snap" package [1] [2]

[1] https://www.engadget.com/2017/12/20/spotify-easier-install-linux/?sr_source=Twitter

[2] https://snapcraft.io/spotify/

I'm getting these errors on spotify startup. I've installed libidn2 but it hasn't changed anything.

/usr/share/spotify/spotify: /usr/lib/libcurl.so.3: no version information available (required by /usr/share/spotify/spotify)

/usr/share/spotify/spotify: /usr/lib/libcurl.so.3: no version information available (required by /usr/share/spotify/spotify)

/proc/self/exe: /usr/lib/libcurl.so.3: no version information available (required by /proc/self/exe)

[1221/171723.780323:ERROR:sandbox_linux.cc(344)] InitializeSandbox() called with multiple threads in process gpu-process.

Trying to launch spotify, i got the following error message

/usr/share/spotify/spotify: /usr/lib/libcurl.so.3: no version information available (required by /usr/share/spotify/spotify)

Fixed with:

sudo pacman -S libidn2

editing the pkgbuild with the following version and checksum works

pkgname=spotify pkgver=1.0.69.336 _anotherpkgver=.g7edcc575 _amd64_pkgrel=39 _i386_pkgrel=39 pkgrel=1 pkgdesc="A proprietary music streaming service" arch=('x86_64' 'i686') license=('custom:"Copyright (c) 2006-2010 Spotify Ltd"') url="http://www.spotify.com" options=('!strip' '!upx')

... sha256sums_x86_64=('ed0dc69f7e50879fcf7bd1bb67e33f08af0c17ebd7bb608ce4e7a143dec1022e')

@rabbitranger @sohakes @sepf @SeerUK

Having the same issue as you guys. It will sporadically seem to start working, but it's upon hitting a button on another song and such that will break it once again.

I haven't found a way to coax it into working properly again yet even when restarting the application and whatnot.

What DE and such are you guys using?

I've managed to patch libcurl-openssl-1.0 to get spotify to work around the CURL_OPENSSL_3 symbol versioning issue. Here are the patches I've used:

https://pastebin.com/xk52rvuv

https://pastebin.com/eKcUqzRC

Could 'we workaround the following issue: /usr/share/spotify/spotify: /usr/lib/libcurl.so.3: no version information available (required by /usr/share/spotify/spotify)

@sohakes @sepf @SeerUK Just randomly started experiencing the same issue. UI locks up when changing songs, takes about 30 seconds to respond.

just installed the package, invoking the app from command line gives "/usr/share/spotify/spotify: error while loading shared libraries: libidn2.so.0: cannot open shared object file: No such file or directory". Maybe a dependency is missing?