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 660897 - gnome-session breaks with pt_BR.iso88591 locale
gnome-session breaks with pt_BR.iso88591 locale
Status: RESOLVED INVALID
Product: gnome-shell
Classification: Core
Component: login-screen
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: Ray Strode [halfline]
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-10-04 17:07 UTC by Daniel Hilst
Modified: 2014-04-28 23:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Daniel Hilst 2011-10-04 17:07:42 UTC 
Hi, my gnome-session breaks after update. I replace the LOCALE=pt_BR.iso88591
 to LOCALE=C on rc.conf, reboot and every thing backs to work. I am using gnome 3.2.0 on archlinux x86_64. 

Here is the ERROR I got on /var/log/gdm/

:0-greeter.log.4:    JS ERROR: !!!   Exception was: Error: Failed to convert UTF-8 string to JS string: Sequ��ncia de bytes inv��lida na entrada de convers��o
:0-greeter.log.4:    JS ERROR: !!!     lineNumber = '0'
:0-greeter.log.4:    JS ERROR: !!!     fileName = '"gjs_throw"'
:0-greeter.log.4:    JS ERROR: !!!     stack = '"("Failed to convert UTF-8 string to JS string: Sequ\xEAncia de bytes inv\xE1lida na entrada de convers\xE3o")@gjs_throw:0
:0-greeter.log.4:    JS ERROR: !!!     message = '"Failed to convert UTF-8 string to JS string: Sequ��ncia de bytes inv��lida na entrada de convers��o"' 


uname -a:
Linux archlinux 3.0-ARCH #1 SMP PREEMPT Tue Aug 30 08:53:25 CEST 2011 x86_64 Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz GenuineIntel GNU/Linux
Comment 1 Vincent Untz 2011-10-04 17:24:18 UTC 
Looks like an issue in the gnome-shell greeter.
Comment 2 Matthias Clasen 2011-10-05 12:37:08 UTC 
Try using pt_BR.utf-8, that is going to work better.
Comment 3 Baptiste Mille-Mathias 2013-04-26 16:00:14 UTC 
Hi there, 

what the status of this bug?
It's unclear to me if the bug is still accurate (Daniel, could you reproduce whith latest version, like 3.8) and if Matthias'answer was a resolution or not.
Comment 4 Florian Müllner 2014-04-28 23:53:13 UTC 
(In reply to comment #3)
> It's unclear to me if the bug is still accurate

Unlikely, closing.