After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 640276 - Banshee Geo Ip detection for Amazon Store Defaults to U.S.
Banshee Geo Ip detection for Amazon Store Defaults to U.S.
Status: RESOLVED FIXED
Product: banshee
Classification: Other
Component: Other Extensions
git master
Other Linux
: Normal normal
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-01-22 17:20 UTC by Chow Loong Jin
Modified: 2011-01-22 17:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Chow Loong Jin 2011-01-22 17:20:31 UTC 
Originally reported at:
  https://bugs.launchpad.net/bugs/706337

Binary package hint: banshee

When I click on the Amazon MP3 store in Banshee (maverick and natty live USB 22 Jan 2011 daily build ) it goes to the U.S. store instead of the U.K. store (I'm in the U.K.). If I right click on Amazon MP3 store and select preferences, it shows Automatic (Geo IP detection) but this doesn't work. It is easy to work around by changing from Automatic to Amazon UK , but it would be better if the Geo IP detection worked.

Note that if RhythmBox is also using Geo IP detection, this seems to work as it always directs me to the Ubuntu One UK store (I've only used this on Maverick).

Please let me know if any further information is required.

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: banshee 1.9.1-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37
Uname: Linux 2.6.37-12-generic i686
Architecture: i386
Date: Sat Jan 22 16:24:38 2011
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110122)
ProcEnviron:
 LANGUAGE=en_US.UTF-8:en
 LANG=en_US.UTF-8
 LC_MESSAGES=en_AG.utf8
 SHELL=/bin/bash
SourcePackage: banshee
Comment 1 Bertrand Lorentz 2011-01-22 17:41:42 UTC 
The server-side redirection was using the wrong country code for the United Kingdom.
Fixed and new version pushed to the server, so the fix is effective immediately.