Description: Ubuntu precise (development branch)
Release: 12.04
gimp:
Installed: 2.6.11-5ubuntu2
Candidate: 2.6.11-5ubuntu2
Version table:
*** 2.6.11-5ubuntu2 0
500 http://de.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
100 /var/lib/dpkg/status
I saved a *.png image (which did find its way to the hard drive, no problems there). The saving dialog would not close but linger for quite a while. Gimp then crashed.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gimp 2.6.11-5ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-8.14-generic-pae 3.2.0
Uname: Linux 3.2.0-8-generic-pae i686
NonfreeKernelModules: fglrx
ApportVersion: 1.90-0ubuntu1
Architecture: i386
Date: Tue Jan 10 00:02:18 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gimp-2.6
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: gimp-2.6 /home/username/Dropbox/Shared/Uni/2011-12\ WiSe/Graphentheorie\ II/agt_vrl/img/2401_003.tif
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xb6a65ca6: movdqu (%edi),%xmm1
PC (0xb6a65ca6) 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: Upgraded to precise on 2012-01-08 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare
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.