GNOME Bugzilla – Bug 684410
Purchase/Import of tracks from Amazon MP fails
Last modified: 2013-02-17 17:22:06 UTC
I can make a purchase, and then I get the creen where it tells me to use Cloud Player, or download now. Clicking download now starts the Amazon plugin, but the GUI feedback just says "Contacting". Nothing more. Looking in .cache/banshee-1 I can see tha .amz files are being cached there, but clicking on one to force a download with Banshee does the same thing. No progress, no song. If I go to the Cloud Player screen within Banshee's browser, select a track and press "Download" nothing happens there either. So this functionality is busted for me completely. I am on Linux Mint 13 64bit. Sample log output: [Info 17:08:09.603] Downloading Amazon MP3 purchase - /home/rob/.cache/banshee-1/temp/Amazon-MP3-1348094218.amz [Info 17:08:15.319] Amazon downloader: waiting for last file to be imported [Info 17:08:15.319] Amazon downloader: last file imported; finishing ...But the song never appears.
I can confirm that this happens to me (banshee 2.4.1 on Ubuntu 12.04). Amazon.com downloads went from "always working" to "never working" fairly recently (i.e. the past few weeks, I think). Same symptoms as reported: the GUI says "Contacting ... " with no further progress.
An update on this. An .amz file obtained from an Amazon purchase at the beginning of November still does not work with banshee. (I get "Contacting ... " then nothing if I open the .amz file with banshee.) The same .amz file works fine with clamz version 0.5-1, which successfully downloads all the tracks. So this problem must be fixable. (Other threads here and there talk about issues with linux and Amazon which are essentially unfixable, or need a workaround such as changing the user agent string in the browser. It seems that this particular bug is not of that sort.)
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 682707 ***