Package Details: spotify 1:

Git Clone URL: (read-only, click to copy)
Package Base: spotify
Description: A proprietary music streaming service
Upstream URL:
Keywords: music player
Licenses: custom
Submitter: gadget3000
Maintainer: AWhetter (NicoHood)
Last Packager: NicoHood
Votes: 2240
Popularity: 31.05
First Submitted: 2010-07-12 12:17
Last Updated: 2021-09-22 08:25

Pinned Comments

NicoHood commented on 2020-05-27 07:46

You can fix the GPG key issue by using:

curl -sS | gpg --import -

Latest Comments

1 2 3 4 5 6 ... Next › Last »

b-fg commented on 2021-10-08 16:54

I also get the no information available error plus this:

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

victorz commented on 2021-10-06 14:04

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

% spotify
spotify: /usr/lib/ no version information available (required by spotify)
/opt/spotify/spotify: /usr/lib/ no version information available (required by /opt/spotify/spotify)
/opt/spotify/spotify: /usr/lib/ no version information available (required by /opt/spotify/spotify)
/proc/self/exe: /usr/lib/ 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).

Zoddo commented on 2021-10-03 10:48

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

TJM commented on 2021-10-03 10:45

makepkg reports an error:

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

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

rbellamy commented on 2021-10-01 01:45

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

Namarrgon commented on 2021-09-30 10:15

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.

rbellamy commented on 2021-09-29 23:42

@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?

Namarrgon commented on 2021-09-29 23:03

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

rad4day commented on 2021-09-29 14:55

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 {} +

sree32 commented on 2021-09-29 14:08

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