This bug was fixed in the package gwibber - 3.4.2-0ubuntu1 --------------- gwibber (3.4.2-0ubuntu1) precise-proposed; urgency=low
* New upstream release. - facebook: Don't crash on unicode characters in a username (LP: #938667) - libgwibber-gtk: Fixed up the GwibberGtkEntry widget's alignment and icon search path (LP: #1011392) * debian/patches/lp_938667.patch - dropped, merged upstream gwibber (3.4.1-0ubuntu1.1) precise-proposed; urgency=low * debian/patches/lp_938667.patch - facebook: Don't crash on unicode characters in a username (LP: #938667) -- Ken VanDine <ken.vand...@canonical.com> Mon, 11 Jun 2012 23:25:25 -0400 ** Changed in: gwibber (Ubuntu Precise) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/938667 Title: gwibber-accounts crashed with UnicodeEncodeError in on_facebook_auth_title_change(): 'ascii' codec can't encode characters in position 0-7: ordinal not in range(128) Status in “gwibber” package in Ubuntu: Fix Released Status in “gwibber” source package in Precise: Fix Released Bug description: Impact: setting up account with non ascii chars fails Test Case: - create a facebook account with a "Š" in your name and try to set it up in gwibber Regression potential: account names could be incorrectly encoded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/938667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp