gimp-2.6 crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECT()

[VF]

Binary package hint: gimp

I've just installed GIMP and tried to start it from KDE's Menu.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gimp 2.6.11-1ubuntu6
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Sun Apr 17 15:55:12 2011
ExecutablePath: /usr/bin/gimp-2.6
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413)
ProcCmdline: /usr/bin/gimp-2.6
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x84d6ff: mov %edx,0x4(%edi)
 PC (0x0084d6ff) ok
 source "%edx" ok
 destination "0x4(%edi)" (0x00000004) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gimp
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_cclosure_marshal_VOID__OBJECT () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gimp-2.6 crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECT()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev sambashare video
XsessionErrors:
 (knotify4:1407): GStreamer-CRITICAL **: gst_debug_add_log_function: assertion `func != NULL' failed
 (gimp-2.6:3895): 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 #748853, 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.