gimp-2.6 crashed with SIGSEGV in g_closure_invoke()

[Roman]

Binary package hint: gimp

I tried twice to run but still comes off error and Gimp will not start

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gimp 2.6.11-1ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
Date: Tue Apr 5 10:57:23 2011
ExecutablePath: /usr/bin/gimp-2.6
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110314)
ProcCmdline: /usr/bin/gimp-2.6
ProcEnviron:
 LANG=uk_UA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ffc96e62c5c: mov 0x50(%rbx),%rdi
 PC (0x7ffc96e62c5c) ok
 source "0x50(%rbx)" (0x00000050) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gimp
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gimp-2.6 crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (knotify4:1562): GStreamer-CRITICAL **: gst_debug_add_log_function: assertion `func != NULL' failed
 (firefox-bin:1764): GLib-CRITICAL **: g_hash_table_insert_internal: assertion `hash_table != NULL' failed
 (gimp-2.6:2053): GLib-WARNING **: /build/buildd/glib2.0-2.28.5/./glib/goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0

[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 #742516, 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.