Encoding errors in gmusicbrowser_1.1.10-0ubuntu1

The patch is for the shimmer-layouts debian patch shipped in Ubuntu 13.10

The attachment "shimmer-layouts patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

This seems to be a problem across the entire package, with encoding errors in the application, translations, and more.

I don't think there is an encoding problem in gmusicbrowser as nobody has complained to me about that, and I haven't made any change that could cause that in a really long time.
Also I've downloaded the debian patch and I don't see the same extra characters, Though there is those strange "Â"s which I don't think should be there at all. By the way the whole shimmer layout patch seems to be wrong, the layouts it adds are already there (I've checked in the gmusicbrowser_1.1.10.orig.tar.gz), though without the strange "Â"s.

So I don't know what is going on there, what are your locale environment variables ? And where else do you see encoding problems other than those strange things added by the layout patch ?

Status changed to 'Confirmed' because the bug affects multiple users.

The the following commit introduced the characters "ÂÂ":

http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/gmusicbrowser/saucy/revision/16/layouts/songtree.layout

The characters can also be found in the "shimmer-layouts" patch in the same commit:

http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/gmusicbrowser/saucy/revision/16/debian/patches/shimmer-layouts

This commit is related to bug #1213158.

Fixed in Debian.

This bug was fixed in the package gmusicbrowser - 1.1.10-2

---------------
gmusicbrowser (1.1.10-2) unstable; urgency=low

  * Fix encoding error in shimmer-layouts patch. (LP: #1234448)

 -- Alessio Treglia <email address hidden> Fri, 11 Oct 2013 19:12:33 +0100

Confirmed: the quickest way to fix this bug is to go to http://gmusicbrowser.org, download the 1.1.10-2 or most recent package, and install it. The slowest way is to wait for it to come in an update package of its own volition.