Closed iheilala closed 10 years ago
Hi again. Mopidy-TuneIn (or any other extension) really should not have this effect. You don't say if Mopidy still worked after installing Mopidy-TuneIn but before rebooting (I expect it continued to work just fine). The fact that this happened previously leads me to think there's something really fishy going on with your SD card, could it be getting corrupted when you reboot? Are you using a reliable power source? Are you using a known good SD card?
Ahh ok I think I might actually have reproduced this on my system... I will get back to you once I've checked some things
I think this might be due to pip installing Mopidy again, so you end up with an installation in /usr/share/mopidy/mopidy
(apt) and /usr/local/lib/python2.7/dist-packages/mopidy
(pip).
sudo pip uninstall mopidy-tunein mopidy
sudo apt-get install mopidy --reinstall
which mopidy
/usr/bin/mopidy
cat /usr/bin/mopidy
#! /usr/bin/python
# EASY-INSTALL-ENTRY-SCRIPT: 'Mopidy==0.18.3','console_scripts','mopidy'
__requires__ = 'Mopidy==0.18.3'
import sys
from pkg_resources import load_entry_point
if __name__ == '__main__':
sys.exit(
load_entry_point('Mopidy==0.18.3', 'console_scripts', 'mopidy')()
)
Enabled extensions: spotify, mpd, local, stream
sudo pip install mopidy-tunein
which mopidy
/usr/bin/mopidy
Enabled extensions: spotify, mpd, local, tunein, stream
sudo pip install --force-reinstall --upgrade mopidy-tunein
which mopidy
/usr/local/bin/mopidy
cat /usr/local/bin/mopidy
#!/usr/bin/python
# -*- coding: utf-8 -*-
import re
import sys
from mopidy.__main__ import main
if __name__ == '__main__':
sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0])
sys.exit(main())
Enabled extensions: mpd, local, tunein, stream
In all three cases Mopidy still works on my system but only the 2nd option gives me all the extensions I want. Something is clearly screwed up here. This was all done with easy_install pip
(v1.5.6) but perhaps the behaviour is different when using python-pip
from apt....
python-pip
from APT (v1.4.1) unsurprisingly made no difference.
But in the words of the great @jodal :
APT-installed extensions will only be found by an APT-installed Mopidy. Pip-installed extensions will be found by both APT- and pip-installed Mopidy.
So obviously we want to be running APT-installed Mopidy and that's why the above 2nd option works. On my system, /usr/local/bin
is later in the path than /usr/bin
and so APT-installed Mopidy gets preference. The --force-reinstall --upgrade
options I used must have removed /usr/bin/mopidy
and allowed the pip-version to run instead.
@iheilala I'm not sure if any of this is actually related to your problem (but I did find it interesting). Perhaps you could ensure the correct APT-version is what's being run? And maybe also try sudo apt-get install mopidy --reinstall
(might want to backup your config file first).
I just realized I can run it /usr/bin/mopidy
and both spotify and tunein works. Thanks again!
I don't really understand why it was picking up the pip version but glad it's working for you. On 6 Jul 2014 15:13, "iheilala" notifications@github.com wrote:
I just realised I can run it /usr/bin/mopidyand both spotify and tunein works. Thanks again!
— Reply to this email directly or view it on GitHub https://github.com/kingosticks/mopidy-tunein/issues/8#issuecomment-48112857 .
I opened mopidy issue #773 and it helped when I reflashed the RPi sd card. Uninstalling and reinstalling mopidy didn't help.
After flashing the sd card I installed mopidy. It worked great. I installed spotify extension and it worked too. I installed TuneIn extension and mopidy stopped working after reboot. It didn't load any extensions and the state was just like the first time I tried to install mopidy (mopidy issue #773) So it seems TuneIn extensions does something to mopidy...
RPi didn't have pip so I installed it before installing TuneIn
sudo apt-get install python-setuptools
sudo easy_install pip