gimp-2.6 crashed with SIGSEGV in file_save_cmd_callback()

[Andres Arenas Velez]

Binary package hint: gimp

Description: Ubuntu lucid (development branch)
Release: 10.04

gimp:
  Installed: 2.6.8-2ubuntu1
  Candidate: 2.6.8-2ubuntu1
  Version table:
 *** 2.6.8-2ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

Could not close GIMP using the windows buttons. Force quit was the only way out.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gimp 2.6.8-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.31-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Apr 15 20:26:05 2010
ExecutablePath: /usr/bin/gimp-2.6
ProcCmdline: gimp-2.6 /home/username/Pictures/Dolphin.png
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x483625 <file_save_cmd_callback+277>: mov 0x8c(%rax),%eax
 PC (0x00483625) ok
 source "0x8c(%rax)" (0x0000008c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gimp
Stacktrace:
 #0 0x0000000000483625 in file_save_cmd_callback ()
 No symbol table info available.
 Cannot access memory at address 0x7fffb524c888
StacktraceTop: file_save_cmd_callback ()
Title: gimp-2.6 crashed with SIGSEGV in file_save_cmd_callback()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner tape video

[Apport retracing service (apport)]

StacktraceTop: file_save_cmd_callback (
ThreadStacktrace:

[Pedro Villavicencio (pedro)]

Looks like bug https://bugzilla.gnome.org/show_bug.cgi?id=614034 ; linking the report, thanks.

[Pedro Villavicencio (pedro)]

do you have any steps on how to reproduce the issue easily? upstream is asking for that information.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.