env crashed with SIGSEGV in setlocale()

[Alexsander Ismere Rodrigues]

desloguei de meu sistema ubunto 10.04 para que um de meus irmãos logasem mas o sistema travou e não abre mas tive de formatar a maquina inteira para poder usala denovo sorry no english este bug não achei na internet.
amd 64 athlon 64 x2 5200, 4gb memoria ram, video geforce9500 gt.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: coreutils 7.4-2ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
Architecture: amd64
Date: Sun Jul 24 14:42:29 2011
ExecutablePath: /usr/bin/env
LiveMediaBuild: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: /usr/bin/env python /usr/lib/cups/backend/hpfax
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF8
SegvAnalysis:
 Segfault happened at: 0x7f624be2fa8f: mov (%rsi),%edx
 PC (0x7f624be2fa8f) ok
 source "(%rsi)" (0xffffffffffffffff) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: coreutils
StacktraceTop:
 ?? () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
 ?? () from /lib/libc.so.6
 setlocale () from /lib/libc.so.6
 ?? ()
Title: env crashed with SIGSEGV in setlocale()
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 _nl_intern_locale_data (category=0, data=0xffffffffffffffff, datasize=256324) at loadlocale.c:78
 _nl_load_locale (file=0x12c1f60, category=0) at loadlocale.c:265
 _nl_find_locale (locale_path=<optimized out>, locale_path_len=<optimized out>, category=0, name=<optimized out>) at findlocale.c:180
 __GI_setlocale (category=0, locale=<optimized out>) at setlocale.c:303
 main (argc=3, argv=0x7fff0296fe98) at env.c:141

[Robert Roth (evfool)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #442272, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.