Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to use spotify, errors on startup #70

Closed
riemers opened this issue Sep 16, 2015 · 8 comments
Closed

Unable to use spotify, errors on startup #70

riemers opened this issue Sep 16, 2015 · 8 comments
Assignees

Comments

@riemers
Copy link

@riemers riemers commented Sep 16, 2015

Default install on mac via pip install, which automaticly adds it to my mopidy installation (something brew did not) but i get below error when i start it up with correct username/pwd and enabled. All other features work as expected, audio, web extensions etc etc.

ERROR    Unhandled exception in SpotifyBackend (urn:uuid:cfd4482b-a530-4ac3-9761-9287ad23e124):
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/site-packages/pykka/actor.py", line 192, in _actor_loop
    self.on_start()
  File "/usr/local/lib/python2.7/site-packages/mopidy_spotify/backend.py", line 53, in on_start
    self._session = self._get_session(self._config)
  File "/usr/local/lib/python2.7/site-packages/mopidy_spotify/backend.py", line 69, in _get_session
    session = spotify.Session(self._get_spotify_config(config))
  File "/usr/local/lib/python2.7/site-packages/spotify/__init__.py", line 58, in wrapper
    return f(*args, **kwargs)
  File "/usr/local/lib/python2.7/site-packages/spotify/session.py", line 60, in __init__
    self.config._sp_session_config, sp_session_ptr))
  File "/usr/local/lib/python2.7/site-packages/spotify/error.py", line 31, in maybe_raise
    raise LibError(error_type)
LibError: Unable to open trace file
ERROR    Actor died: SpotifyBackend (urn:uuid:cfd4482b-a530-4ac3-9761-9287ad23e124) stopped before handling the message

Also don't know where it tries to make a trace file, otherwise that might have showed something?

Updated: Removed ref to unrelated GMusic bug. -jodal

@jodal
Copy link
Member

@jodal jodal commented Sep 16, 2015

I'm fixing this in one in pyspotify now. New release out soon.

@jodal jodal self-assigned this Sep 16, 2015
@riemers
Copy link
Author

@riemers riemers commented Sep 16, 2015

👍

@jodal
Copy link
Member

@jodal jodal commented Sep 22, 2015

pyspotify 2.0.5 is out now. It should fix this.

@riemers
Copy link
Author

@riemers riemers commented Sep 22, 2015

Thanks this seems to have fixed that issue. Installed it via pip install -e alreayd, only to get the next hurdle.

ERROR    Spotify login error: <ErrorType.OTHER_PERMANENT: 10>

but nothing on the internet states a root cause for this. But i assume this is coming back from spotify so in reality you cannot help with that am i correct?

@jodal
Copy link
Member

@jodal jodal commented Sep 22, 2015

That's a login error returned from Spotify's servers through libspotify and pyspotify. Check your username and password, and that you have a premium account. Also watch out for other log messages that might be more helpful.

@riemers
Copy link
Author

@riemers riemers commented Sep 22, 2015

Comes back with

  libspotify log message: 10:04:22.800 I [offline_authorizer.cpp:297] Unable to login offline: no such user
  libspotify log message: 10:04:22.813 E [ap:1694] AP Socket Error: Host not found (20001)

I am using a proxy here, perhaps that is causing problems?

@jodal
Copy link
Member

@jodal jodal commented Sep 22, 2015

If you google "AP Socket Error: Host not found (20001)" it seems to be a general problem with Spotify and proxying. Let me know if anything indicates anything wrong in Mopidy-Spotify and/or pyspotify.

@riemers
Copy link
Author

@riemers riemers commented Sep 22, 2015

I just did a test, with direct connection without any proxy's. It works like a charm, so it has nothing to do with mopidy/psypotify. I also see its connecting through a non default proxy port to get to the AP so that will not work with the proxy in question here. Anyways, thanks for the quick help, i'll resort to other 'internet' connections to get this working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants