As mentioned in the GitHub issue before it was closed: it’s spelled “Mopidy”, not “Modipy”. Try using the correct command name, and it’ll hopefully work a bit better
Sooo it effectively answer ( ) but not exactly as i wanted… :
Traceback (most recent call last):
File “/usr/bin/mopidy”, line 7, in
from mopidy.main import main
File “/usr/lib64/python2.7/site-packages/mopidy/main.py”, line 28, in
from mopidy import commands, config as config_lib, ext
File “/usr/lib64/python2.7/site-packages/mopidy/commands.py”, line 14, in
from mopidy.audio import Audio
File “/usr/lib64/python2.7/site-packages/mopidy/audio/init.py”, line 4, in
from .actor import Audio
File “/usr/lib64/python2.7/site-packages/mopidy/audio/actor.py”, line 8, in
import pygst
ImportError: No module named pygst
I feel a bit confused now i already saw that ( yeaah i’ve wrote the right command once ) but i didn’t found how to install this “pygst” if i’m good understanding it’s this “Gsteamer”
Let’s find out >__<
Thanks for helping and i apologie for my stupidity hehe
FOR INFO: in the terminal answer, the “main” is a simple main with two “_” before and after it
I don’t know why but gstreamer wasn’t good installed, so i just entered :
yum install gstreamer-python
and then i don’t have the error. i mean not the same
I have a problem for the local files :
INFO Disabled extensions: local
WARNING Found local configuration errors, the extension has been automatically disabled:
WARNING local/media_dir must be set.
WARNING Please fix the extension configuration errors or disable the extensions to silence these messages.
There’s no relation between the dir that Mopidy is installed in and the media dir. Also, the error you see is a config error, which relates to reading of the config files, not if the actual dir can be found or not. If it can read the config and the dir doesn’t exist, it’ll simply be created.
Use mopidy config to check what’s Mopidy’s view of the config file. Also, the first few lines of output from mopidy should print what config files it finds and uses. If you run mopidy -v, it’ll also print config file locations it checks if exists.
WARNING 2015-04-05 02:28:40,468 [15607:MainThread] mopidy.__main__
Found local configuration errors, the extension has been automatically disabled:
WARNING 2015-04-05 02:28:40,468 [15607:MainThread] mopidy.__main__
local/media_dir must be set.
WARNING 2015-04-05 02:28:40,468 [15607:MainThread] mopidy.__main__
Please fix the extension configuration errors or disable the extensions to silence these messages.
i’ve edited it but it still don’t work, it’s nor comented out… for the record, mopidy config shows the same thing that before… few first lines of mopidy command says that config file are
/root/.config/mopidy/mopidy.conf
So i’m supposing to be good… maybe i’m wrong in the entrances at [Local]'s lines?
If mopidy prints /root/.config/mopidy/mopidy.conf as the config file in use,
And /root/.config/mopidy/mopidy.conf contains:
[local]
media_dir = /some/path
Then mopidy config should show the same media_dir path.
If not, there’s probably something wrong with the syntax in your config file. Try changing another config and see if you can see the change in mopidy config.