gimp-2.6 crashed with SIGSEGV

Bug #1119410 reported by Benjamin
This bug report is a duplicate of:  Bug #912909: gimp-2.6/2.8 crashed with SIGSEGV. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gimp (Ubuntu)
New
Undecided
Unassigned

Bug Description

Crash during "save as..." one edit outed png picture without compression.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gimp 2.6.12-1ubuntu1.2
ProcVersionSignature: Ubuntu 3.2.0-37.58-generic-pae 3.2.35
Uname: Linux 3.2.0-37-generic-pae i686
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: i386
CrashCounter: 1
Date: Fri Feb 8 14:48:19 2013
ExecutablePath: /usr/bin/gimp-2.6
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
MarkForUpload: True
ProcCmdline: gimp-2.6 /home/username/Bilder/2013/02/08/IMG_0020.JPG
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb69bf756: movdqu (%edi),%xmm1
 PC (0xb69bf756) ok
 source "(%edi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gimp
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
Title: gimp-2.6 crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

Revision history for this message
Benjamin (nailartcenter) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #912909, 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.

information type: Private → Public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.