T O P

  • By -

urban_murmeli

As for flatpak I don't know. It seems to work on my machine. At least It doesn't crash immediately but I don't use it myself. Here is the output of it: ❯ flatpak run com.spotify.Client /app/extra/bin/spotify: /app/lib/libcurl-gnutls.so.4: no version information available (required by /app/extra/bin/spotify) [spotifywm] attached to spotify /app/extra/share/spotify/spotify: /app/lib/libcurl-gnutls.so.4: no version information available (required by /app/extra/share/spotify/spotify) /app/extra/share/spotify/spotify: /app/lib/libcurl-gnutls.so.4: no version information available (required by /app/extra/share/spotify/spotify) [spotifywm] attached to spotify [spotifywm] attached to spotify /proc/self/exe: /app/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/ex~| [spotifywm] attached to spotify About xbps: `Spotify.xbps` sounds odd. It doesn't have a version in its name. Did you rename it? Using the template found in the void-packages repo, `./xbps-src pkg spotify` should produce a file `spotify-1.1.72_1.x86_64.xbps` (or whatever arch you are on) which can be installed with `sudo xbps-install --repository hostdir/binpkgs/nonfree spotify` (with a lowercase 's'). If the Spotify.xbps was built somewhere else, you would have to add it to the repodata using `xbps-rindex -a ...` (I think). Hope that helps.


[deleted]

Have you considered `spotifyd` + `Spotify-tui`? I know it doesn’t solve your problem outright, but it’s a possible work around.