kraxarn
spotifyd 0.3.5 Client unsupported
System information
ABI : x86_64-little_endian-lp64 App version : v3.12 Build type : Release Current desktop: MATE D-Bus support : Yes Install type : System KCrash support : No Kernel : linux 6.13.5-200.fc41.x86_64 Platform : xcb Product : Fedora Linux 41 (MATE-Compiz) Qt version : 6.8.2
Detailed information
Installed spotify-qt from copr (https://copr.fedorainfracloud.org/coprs/kraxarn/spotify-qt) and spotifyd (https://copr.fedorainfracloud.org/coprs/mbooth/spotifyd/) on Fedora 41
What happens?
Selected /usr/bin/spotifyd as a client and when I try to start it I get this:
What should happen?
Guess spotifyd should start.
I am having the same issue but for librespot. Exact same error message after first install of both. I am new to linux in general so this may be on me but if not, then here is some info. Running Fedora Linux 41 XFCE running on a 2012 Macbook Air.
ABI : x86_64-little_endian-lp64 App version : v3.12 (94a60199) Build type : Current desktop: XFCE D-Bus support : Yes KCrash support : No Kernel : linux 6.13.6-200.fc41.x86_64 Platform : xcb Product : Ubuntu Core 18 Qt version : 5.9.5
Any steps to try and solve are appreciated. I am also unsure exactly what I am being asked to upgrade by the error message, both are just installed so I imagine they are the latest versions available to me.
Spotify changed its login. You now need OAuth, which is only supported up from spotifyd 0.4 or librespot 0.5 onwards:
https://github.com/Spotifyd/spotifyd/releases/tag/v0.4.0 https://github.com/librespot-org/librespot/releases/tag/v0.5.0
Older versions won't connect to Spotify any more and spotify-qt will give you the above error message. Also @GordonRamsay-689 Qt 5.9 is from 2017 and EOL since 2020. What source of spotify-qt are your using?
I see, then I need to get spotify-qt from a more up to date source? I was using the Snap. I could test some other source and see if that works better.
EDIT: I installed using the Copr repo with dnf instead and now it all works as expected. I got stuck for a minute as I was providing the relative path (~) instead of /home/usr/ for librespot, but once I put the full expanded path instead it all worked fine. Thank you!
I was using the Snap
Does the snap come with librespot or do you have to provide it through other sources? @kraxarn since you are maintaining the snap by yourself, could you update the dependencies?
I was using the Snap
Does the snap come with librespot or do you have to provide it through other sources?
The snap did not come with librespot (I don't think it is supposed to as you can use any daemon like spotifyd optionally). I installed librespot with Cargo following the instructions on the librespot Github.
As an aside I am not sure if the Copr came with it either because at that point I already had librespot installed.
Support for spotifyd v0.4.0 should be kind of supported as of baeae33260fdf9bc56abbc28c7dd12e5a6af8d06, but due to the major changes, and different behaviour from librespot, I've decided to deprecate support for it. librespot is already well supported, and makes more sense when not running as a daemon, so please use librespot directly instead.
The snap is provided by me, but it's very abandoned right now. I wanted to wait until I had Flatpak support with deprecating it, but due to difficulties maintaining it, I might deprecate it sooner than that, unless someone wants to step up and maintain it instead 😄
