Bug 704655 - [abrt] gimp-2:2.6.11-6.fc14: _g_utf8_normalize_wc: Process /usr/bin/gimp-2.6 was killed by signal 11 (SIGSEGV)
Summary: [abrt] gimp-2:2.6.11-6.fc14: _g_utf8_normalize_wc: Process /usr/bin/gimp-2.6 ...
Keywords:
Status: CLOSED DUPLICATE of bug 630405
Alias: None
Product: Fedora
Classification: Fedora
Component: gimp
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8aa9c7e80242a11a78a5a68739a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-13 21:18 UTC by philippeM
Modified: 2011-09-05 07:39 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-09-05 07:39:25 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (71.46 KB, text/plain)
2011-05-13 21:18 UTC, philippeM 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.