GNOME Bugzilla – Bug 523679
Jamendo is loading catalogue forever
Last modified: 2008-04-05 10:35:13 UTC
Please describe the problem: When I open Rhythmbox and click on Jamendo, the Jamendo splash page displays and the load progress bar displays in lower left. When the progress bar completes, the songs on Jamendo don't display. This only happens the one time when there is no XML database file under ~/.gnome2/rhythmbox/jamendo/. On subsequent tries (XML database exists) the progress bar never completes and the songs again don't display. Steps to reproduce: 1. Start Rhythmbox 2. Click on Jamendo in the left side pane 3. The Jamendo splash page and the progress bar (lower left) displays 4. When the progress bar completes the songs don't display 5. On subsequent tries (restart Rhythmbox) the progress bar never completes Actual results: The Jamendo splash page never switches to show the songs on Jamendo. Expected results: I would expect the songs on Jamendo to display. Does this happen every time? Yes Other information: When I started Rhythmbox from the Gnome terminal and followed the steps I got the followin... Traceback (most recent call last):
+ Trace 193010
parser.feed(data)
self._err_handler.fatalError(exc)
raise exception
Yep, it appears that something broke the jamendo plugin. I can reproduce this, here is my traceback Traceback (most recent call last):
+ Trace 193196
parser.close()
self.feed("", isFinal = 1)
Traceback (most recent call last): File "/usr/local//lib/rhythmbox/plugins/jamendo/JamendoSource.py", line 156, in finish_loadscreen self.__load_db () File "/usr/local//lib/rhythmbox/plugins/jamendo/JamendoSource.py", line 289, in __load_db tracks = self.__saxHandler.tracks AttributeError: JamendoSaxHandler instance has no attribute 'tracks' The downloaded catalog appears to be well-formed (checked it using "xmllint --noout") Cc'ing the original Jamendo plugin author.
Alex: your error doesn't seem to be the same as the original report. See my comment on https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/203428
You are right it doesn't appear to be quite the same, although it is an error from reading the XML, but it seems not to be able find an element "<unknown>:1:0: no element found", rather than the XML not being well-formed I checked manually and found that the XML is indeed well-formed, so there must be some other error in the XML>
*** Bug 524141 has been marked as a duplicate of this bug. ***
*** Bug 524186 has been marked as a duplicate of this bug. ***
I've seen this reported downstream as well: https://bugzilla.redhat.com/show_bug.cgi?id=437402 Checked all the obvious (truncated/not well formed XML, broken temp file, outdated DTD, etc.) and couldn't come up with an explanation.
*** Bug 524284 has been marked as a duplicate of this bug. ***
Hi, Note that when I see this problem there is no traceback. The XML is parsed fine, it's just that there is no longer the required information in the dbdump from Jamendo. I reported this to them at http://www.jamendo.com/en/forums/discussion/3242/database-dumps-no-longer-contain-track-information/ Hopefully it will be rectified. Thanks, James
My contact at Jamendo told me this should be fixed.
Yes, it's working again now. Thanks for passing that on.