Ubuntu
banshee package

Banshee does not show song recommendations

Bug #86892 reported by aamukahvi
2
Affects Status Importance Assigned to Milestone
Banshee
Fix Released
Medium
banshee (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: banshee

I have enabled Music Recommendations plugin and View → Show Recommendations is ticked.

Console output:
------------------------------------------------------------------------
$ banshee
Debug: [2/22/2007 1:24:18 AM] (Loading audio profiles) - /usr/share/banshee/audio-profiles
0:00:00.940618000 27883 0x823f078 ERROR GST_PIPELINE ./grammar.y:494:_gst_parse__yyparse: no element "xingenc"
0:00:00.962599000 27883 0x823f078 ERROR GST_PIPELINE ./grammar.y:494:_gst_parse__yyparse: no element "fluwmaenc"
0:00:00.963876000 27883 0x823f078 ERROR GST_PIPELINE ./grammar.y:494:_gst_parse__yyparse: no element "fluasfmux"
Debug: [2/22/2007 1:24:19 AM] (Default player engine) - GStreamer 0.10
Debug: [2/22/2007 1:24:19 AM] (Audio CD Core Initialized) -
Debug: [2/22/2007 1:24:19 AM] (Testing device for DAP support) - /org/freedesktop/Hal/devices/volume_uuid_52F4F56FF4F555A7
Debug: [2/22/2007 1:24:19 AM] (Waiting for possible DAP to mount) - /org/freedesktop/Hal/devices/volume_uuid_52F4F56FF4F555A7
Debug: [2/22/2007 1:24:19 AM] (DAP has not been added) - /org/freedesktop/Hal/devices/volume_uuid_52F4F56FF4F555A7
: Could not grab key 160 (maybe another application has grabbed this key)
: Could not grab key 151 (maybe another application has grabbed this key)
: Could not grab key 144 (maybe another application has grabbed this key)
: Could not grab key 153 (maybe another application has grabbed this key)
Setting IO Backend to Banshee.IO.Unix.IOConfig (unix)
Could not fetch recommendations: The remote server returned an error: (404) Not Found.

Revision history for this message
aamukahvi (aamukahvi) wrote :

Ubuntuforums thread:
http://www.ubuntuforums.org/showthread.php?p=2191077#post2191077

Revision history for this message
aamukahvi (aamukahvi) wrote :

Also I get "hostname could not be parsed":
---------------------------------------
Could not fetch recommendations: The remote server returned an error: (404) Not Found.
Could not fetch recommendations: Invalid URI: The hostname could not be parsed
Could not fetch recommendations: Invalid URI: The hostname could not be parsed
Could not fetch recommendations: Invalid URI: The hostname could not be parsed
Could not fetch recommendations: The remote server returned an error: (404) Not Found.
Could not fetch recommendations: The remote server returned an error: (404) Not Found.
Could not fetch recommendations: Invalid URI: The hostname could not be parsed

Revision history for this message
Sebastian Dröge (slomo) wrote :

This is already fixed upstream... we will get the fix with the next release

Changed in banshee:
status: Unconfirmed → Fix Committed
Revision history for this message
Andrew Conkling (andrewski) wrote :

This fix has been released in Feisty; does that make this "Released" as far as this bug is concerned?

Bug Watch Updater (bug-watch-updater)
Changed in banshee:
status: Unknown → Fix Released
Revision history for this message
Sebastian Dröge (slomo) wrote :

It's not fixed in feisty, only in banshee SVN. It will work sometimes, but sometimes one will get the original bug too.

I'll either backport the fix from SVN next week or try to get the next banshee release into feisty...

Revision history for this message
Wouter Stomp (wouterstomp-deactivatedaccount) wrote :

This fix should be in ubuntu now.

Changed in banshee:
status: Fix Committed → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in banshee:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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