mopidy
Warning mopidy.config : Ignoring config section 'spotify' because no matching extension was found
Hi i installed the extension but they keep telling me that the config file doesn't found it. It may sound stupid but i think i've checked everything maybe just a problem of path with pip ? I think i've followed the instructions of installations, if someone can check with me to see another point of view it would be awesome thanks :)
Did you follow the installation instructions at https://github.com/mopidy/mopidy-spotify?tab=readme-ov-file#installation
If you did, the next step is to provide your deps as per https://docs.mopidy.com/stable/troubleshooting/#show-installed-dependencies
Did you follow the installation instructions at https://github.com/mopidy/mopidy-spotify?tab=readme-ov-file#installation
If you did, the next step is to provide your deps as per https://docs.mopidy.com/stable/troubleshooting/#show-installed-dependencies
Hi, yes i've followed the instructions i think. I have checked that i have installed the plugins for Gstream and i used the exact pip command line.
In my deps i'm missing flump3dec and mad i think
WARNING 2025-08-13 11:54:47,070 [60239:MainThread] mopidy.config
Ignoring config section 'spotify' because no matching extension was found
Executable: /usr/bin/mopidy
Platform: Linux-6.16.0-cachyos2.fc42.x86_64-x86_64-with-glibc2.41
Python: CPython 3.13.5 from /usr/lib64/python3.13
mopidy: 4.0.0a4 from /usr/lib/python3.13/site-packages
pydantic: 2.10.6 from /usr/lib/python3.13/site-packages
annotated-types: 0.7.0 from /usr/lib/python3.13/site-packages
typing-extensions: 4.12.2 from /usr/lib/python3.13/site-packages
pydantic-core: 2.27.2 from /usr/lib64/python3.13/site-packages
pygobject: 3.50.0 from /usr/lib64/python3.13/site-packages
pykka: 4.2.0 from /usr/lib/python3.13/site-packages
requests: 2.32.4 from /usr/lib/python3.13/site-packages
charset-normalizer: 3.4.1 from /usr/lib/python3.13/site-packages
idna: 3.10 from /usr/lib/python3.13/site-packages
urllib3: 2.3.0 from /usr/lib/python3.13/site-packages
setuptools: 74.1.3 from /usr/lib/python3.13/site-packages
tornado: 6.4.1 from /usr/lib64/python3.13/site-packages
GStreamer: 1.26.5.0 from /usr/lib64/python3.13/site-packages/gi
Detailed information:
Python wrapper: python-gi 3.50.0
Relevant elements:
Found:
uridecodebin: 1.26.5
souphttpsrc: 1.26.5
spotifyaudiosrc: 0.15.0-alpha.1-357336cd
alsasink: 1.26.5
osssink: 1.26.5
oss4sink: 1.26.5
pulsesink: 1.26.5
id3demux: 1.26.5
id3v2mux: 1.26.5
lamemp3enc: 1.26.5
mpegaudioparse: 1.26.5
mpg123audiodec: 1.26.5
vorbisdec: 1.26.5
vorbisenc: 1.26.5
vorbisparse: 1.26.5
oggdemux: 1.26.5
oggmux: 1.26.5
oggparse: 1.26.5
flacdec: 1.26.5
flacparse: 1.26.5
shout2send: 1.26.5
Not found:
flump3dec
mad
Interesting, it can't find it. This is fedora? Pip install paths should have been a problem solved years ago . Can you try reinstalling Mopidy-Spotify and share the output. Maybe add -v (or whatever it is) for verbose logging?
Yes it is Fedora Workstation ! And yes of course, i have tried this earlier but it's clearly possible that i have missed something haha
sudo python3 -m pip install --break-system-packages mopidy-spotify==5.0.0a3 -v
Using pip 24.3.1 from /usr/lib/python3.13/site-packages/pip (python 3.13)
Collecting mopidy-spotify==5.0.0a3
Obtaining dependency information for mopidy-spotify==5.0.0a3 from https://files.pythonhosted.org/packages/ec/b1/c9c6f7c22629e2511edc400e552e9f89118350dac5d3b6828c09b7deb545/Mopidy_Spotify-5.0.0a3-py3-none-any.whl.metadata
Using cached Mopidy_Spotify-5.0.0a3-py3-none-any.whl.metadata (7.0 kB)
Requirement already satisfied: Mopidy>=3.4.0 in /usr/lib/python3.13/site-packages (from mopidy-spotify==5.0.0a3) (4.0.0a4)
Requirement already satisfied: Pykka>=2.0.1 in /usr/lib/python3.13/site-packages (from mopidy-spotify==5.0.0a3) (4.2.0)
Requirement already satisfied: requests>=2.20.0 in /usr/lib/python3.13/site-packages (from mopidy-spotify==5.0.0a3) (2.32.4)
Requirement already satisfied: setuptools in /usr/lib/python3.13/site-packages (from mopidy-spotify==5.0.0a3) (74.1.3)
Requirement already satisfied: pydantic>=2.9 in /usr/lib/python3.13/site-packages (from Mopidy>=3.4.0->mopidy-spotify==5.0.0a3) (2.10.6)
Requirement already satisfied: pygobject>=3.42 in /usr/lib64/python3.13/site-packages (from Mopidy>=3.4.0->mopidy-spotify==5.0.0a3) (3.50.0)
Requirement already satisfied: tornado>=6.2 in /usr/lib64/python3.13/site-packages (from Mopidy>=3.4.0->mopidy-spotify==5.0.0a3) (6.4.1)
Requirement already satisfied: charset-normalizer<4,>=2 in /usr/lib/python3.13/site-packages (from requests>=2.20.0->mopidy-spotify==5.0.0a3) (3.4.1)
Requirement already satisfied: idna<4,>=2.5 in /usr/lib/python3.13/site-packages (from requests>=2.20.0->mopidy-spotify==5.0.0a3) (3.10)
Requirement already satisfied: urllib3<3,>=1.21.1 in /usr/lib/python3.13/site-packages (from requests>=2.20.0->mopidy-spotify==5.0.0a3) (2.3.0)
Requirement already satisfied: annotated-types>=0.6.0 in /usr/lib/python3.13/site-packages (from pydantic>=2.9->Mopidy>=3.4.0->mopidy-spotify==5.0.0a3) (0.7.0)
Requirement already satisfied: pydantic-core==2.27.2 in /usr/lib64/python3.13/site-packages (from pydantic>=2.9->Mopidy>=3.4.0->mopidy-spotify==5.0.0a3) (2.27.2)
Requirement already satisfied: typing-extensions>=4.12.2 in /usr/lib/python3.13/site-packages (from pydantic>=2.9->Mopidy>=3.4.0->mopidy-spotify==5.0.0a3) (4.12.2)
Using cached Mopidy_Spotify-5.0.0a3-py3-none-any.whl (26 kB)
Installing collected packages: mopidy-spotify
Successfully installed mopidy-spotify-5.0.0a3
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
What about the warning on the last line ? Does that mean it didn't actually install anything?! Why are they so hell bent on breaking system install whilst offering no viable alternative for services.
Yeah that's kinda true it's the first time i'm trying to use an MPD and Mopidy i'm learning on the go and feel a Little bit confused with that break system :)
Yes, i have also tried without the sudo command to install it with my user i guess but it seems that it doesn't change a lot.
Anyway i'm grateful that somebody is helping me with that i was feeling a Little bit lost x)
Is there a mopidy_spotify-5.0.0a3 folder in /usr/lib/python3.13/site-packages ? or /usr/local/lib/python3.13/site-packages ?
That is where it's supposed to be for something installed via pip on Fedora. Debian and Fedora work slightly differently w.r.t this and maybe something installed via your package manager (in /usr/lib/python3.13/site-packages) cannot see something installed via pip (in /usr/local/lib/python3.13/site-packages ). It should be able to. This mess should have been fixed by them years and years ago. I don't understand why they'd intentionally want it to be broken like this. Confused. @jodal ?
Yeah confused too, i have checked again to be sure and i only have these /usr/lib/python3.13/site-packages/mopidy-4.0.0a4.dist-info, /usr/lib/python3.13/site-packages/mopidy with the mopidy name
Sorry to be so late to the party!
The next thing I would have checked was what that Python's search path actually included /usr/local/lib/python3.13/site-packages. You can do that by running:
sudo python3
And then in the Python REPL:
import sys
sys.path
On my Debian system this looks like the following, where /usr/local/lib/python3.13/dist-packages is the equivalent path on Debian systems, where packages installed with sudo python3 -m pip install --break-system-packages ... will end up:
❯ sudo python3
Python 3.13.5 (main, Jun 25 2025, 18:55:22) [GCC 14.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.path
['', '/usr/lib/python313.zip', '/usr/lib/python3.13', '/usr/lib/python3.13/lib-dynload',
'/usr/local/lib/python3.13/dist-packages', '/usr/lib/python3/dist-packages']
>>>
