Bug 704655

Summary: [abrt] gimp-2:2.6.11-6.fc14: _g_utf8_normalize_wc: Process /usr/bin/gimp-2.6 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: philippeM <pmauguin>
Component: gimpAssignee: Nils Philippsen <nphilipp>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: nphilipp, xion.luhnis
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:8aa9c7e80242a11a78a5a68739ad3d905bd30c7a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-09-05 07:39:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description philippeM 2011-05-13 21:18:37 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 73177 bytes
cmdline: gimp-2.6
component: gimp
Attached file: coredump, 166182912 bytes
crash_function: _g_utf8_normalize_wc
executable: /usr/bin/gimp-2.6
kernel: 2.6.35.13-91.fc14.i686.PAE
package: gimp-2:2.6.11-6.fc14
rating: 4
reason: Process /usr/bin/gimp-2.6 was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1305321931
uid: 500

How to reproduce
-----
1.work inside GIMP 
2.export as JPG (save)
3.save under new name as JPG

Comment 1 philippeM 2011-05-13 21:18:40 UTC
Created attachment 498864 [details]
File: backtrace

Comment 2 Xion Luhnis 2011-09-04 23:35:35 UTC
Package: gimp-2:2.6.11-16.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Create a new document on Gimp
2. Save it as a new png file

Comment
-----
If the png file already exists (or while overwriting one), it doesn't crash, but if the png file is new, it always crashes gimp.

Comment 3 Nils Philippsen 2011-09-05 07:39:25 UTC

*** This bug has been marked as a duplicate of bug 630405 ***