gimp-2.6 crashed with SIGSEGV in g_utf8_normalize()

[Gen X]

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
Description: Ubuntu oneiric (development branch)
Release: 11.10

2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
gimp:
  Instalados: 2.6.11-2ubuntu3
  Candidato: 2.6.11-2ubuntu3
  Tabla de versión:
 *** 2.6.11-2ubuntu3 0
        500 http://mx.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
        100 /var/lib/dpkg/status

3) What you expected to happen
chnge image format. png to jpg

4) What happened instead
ginp change the format, after that crash

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gimp 2.6.11-2ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-11.18-usernameeric 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 17 21:52:57 2011
ExecutablePath: /usr/bin/gimp-2.6
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: gimp-2.6 /home/username/Escritorio/Pantallazo\ de\ 2011-09-17\ 21:51:31.png
SegvAnalysis:
 Segfault happened at: 0x7fa34bbc824a: cmpb $0x0,(%rbx)
 PC (0x7fa34bbc824a) ok
 source "$0x0" ok
 destination "(%rbx)" (0x00000080) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gimp
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_utf8_normalize () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
Title: gimp-2.6 crashed with SIGSEGV in g_utf8_normalize()
UpgradeStatus: Upgraded to oneiric on 2011-09-13 (4 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #849288, so 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. Please continue to report any other bugs you may find.