Audioscrobbler stops working after a while

Bug #542907 reported by Fernando Irías Escher
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Exaile
Triaged
Medium
Unassigned

Bug Description

When I start Exaile, it is scrobbling everything fine, but after a while, it seems that it cannot open the post url. Some terminal details here:

INFO : Attempting to submit "Now Playing" information to AudioScrobbler...
Exception in thread Thread-27:
Traceback (most recent call last):
  File "/usr/lib/python2.6/threading.py", line 525, in __bootstrap_inner
    self.run()
  File "/usr/lib/python2.6/threading.py", line 477, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/share/exaile/plugins/audioscrobbler/__init__.py", line 187, in now_playing
    track.get_duration(), track.get_track())
  File "/usr/share/exaile/plugins/audioscrobbler/_scrobbler.py", line 182, in now_playing
    login(__LOGIN['u'], __LOGIN['p'], client=__LOGIN['c'])
  File "/usr/share/exaile/plugins/audioscrobbler/_scrobbler.py", line 88, in login
    response = urllib2.urlopen(req)
  File "/usr/lib/python2.6/urllib2.py", line 124, in urlopen
    return _opener.open(url, data, timeout)
  File "/usr/lib/python2.6/urllib2.py", line 381, in open
    protocol = req.get_type()
  File "/usr/lib/python2.6/urllib2.py", line 242, in get_type
    raise ValueError, "unknown url type: %s" % self.__original
ValueError: unknown url type: post.audioscrobbler.com?a=<some hash>&c=exa&hs=true&p=1.2&u=<my username>&t=<some number>&v=0.3.0

I changed the <my username>, <some hash> and <some number> values for security. Hope this get solved soon.

Thanks!

Revision history for this message
Johannes Sasongko (sjohannes) wrote :

> ValueError: unknown url type: post.audioscrobbler.com?a=<some hash>&c=exa&hs=true&p=1.2&u=<my username>&t=<some number>&v=0.3.0

Hmm, missing http:// ?

Changed in exaile:
importance: Undecided → Medium
milestone: none → 0.3.1.1
status: New → Triaged
Revision history for this message
Harry (hellfroze) wrote :

I get an identical error after exaile had been running for a while scrobbling OK but then paused for an extended period (overnight, for example). Once it starts erroring like this, it doesn't recover on its own but if I restart it, it works OK.

However, I think it may be related to my comment in this bug https://bugs.launchpad.net/exaile/+bug/518939 in that if I don't catch it and restart shortly after the problem occurs, a long queue of scrobbles forms and then causes other errors related to *that*.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.