gimp-2.6 crashed with SIGSEGV in file_save_cmd_callback()

[wrabacon]

Binary package hint: gimp

Program Froze while shutting down.

ProblemType: Crash
Architecture: i386
Date: Wed Mar 24 22:30:18 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gimp-2.6
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113)
Package: gimp 2.6.8-2ubuntu1
ProcCmdline: gimp-2.6 /usr/share/games/wormux/map/icebergs/map.png
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
SegvAnalysis:
 Segfault happened at: 0x80b8946 <file_save_cmd_callback+278>: mov 0x58(%eax),%ecx
 PC (0x080b8946) ok
 source "0x58(%eax)" (0x00000058) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gimp
StacktraceTop:
 file_save_cmd_callback ()
 g_cclosure_marshal_VOID(int0_t) ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Title: gimp-2.6 crashed with SIGSEGV in file_save_cmd_callback()
Uname: Linux 2.6.32-17-generic i686
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 file_save_cmd_callback (action=0x9d76438, value=3,
 g_signal_list_ids () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 g_signal_connect_data () from /usr/lib/libgobject-2.0.so.0
 g_type_class_get_private ()

[Pedro Villavicencio (pedro)]

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version.Thanks in advance.

[Pedro Villavicencio (pedro)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.