Hi,
starting today the beloved gstreamer error appeared again.
ERROR [MainThread] mopidy.audio.gst GStreamer error: Resource not found.
Currently the Pi runs gst-plugin-spotify_0.15.0.alpha.1-4_armhf.deb
Anyone affected too?
Yup. Me too. I am getting totally sick of Spotify. They are so sh***y on so many counts. Why pay just to be abused?
Can’t even get a track list now…
Can you retry with the detailed debug logging enabled:
GST_DEBUG=librespot:6,spotifyaudiosrc:4 GST_DEBUG_LIBRESPOT=DEBUG mopidy
(FYI I can’t reproduce this).
WARNING 2025-12-15 20:06:46,248 [1654:MainThread] mopidy._main_
Found spotify configuration errors. The extension has been automatically disabled:
WARNING 2025-12-15 20:06:46,253 [1654:MainThread] mopidy._main_
spotify/client_id must be set.
WARNING 2025-12-15 20:06:46,260 [1654:MainThread] mopidy._main_
spotify/client_secret must be set.
WARNING 2025-12-15 20:06:46,266 [1654:MainThread] mopidy._main_
Please fix the extension configuration errors or disable the extensions to silence these messages.
I am getting these warnings; not sure where these came from…
Is this because I normally run mopidy as a service on an RPi?
That’s weird. We are back on again. Perhaps just a service glitch at Spotify? Thanks for responding like lightning as usual, Nick. (“Quick Nick, Kingofsticks”?). Will let you know if it resurfaces, but I’ll give it a days or so next time.
Yes. That’ll be why. I think for next time you can set the environment variables in the systemd service control file but I don’t have the specifics/example of that to hand.
Glad it’s working. Hopefully just an transient issue one one of their servers… I think we may have seen a report of it on librespot repo around the same time, but without the logs it’s impossible to say it was the same underlying issue.