Bug 630405 - [abrt] gimp-2:2.6.10-5.fc14: _g_utf8_normalize_wc: Process /usr/bin/gimp-2.6 was killed by signal 11 (SIGSEGV)
Summary: [abrt] gimp-2:2.6.10-5.fc14: _g_utf8_normalize_wc: Process /usr/bin/gimp-2.6 ...
Keywords:
Status: CLOSED DUPLICATE of bug 716325
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk2
Version: 14
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0e171c68712987fd30f17fe82bd...
: 630362 636648 637334 672738 704655 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-05 11:46 UTC by Pavel Ondračka
Modified: 2012-01-18 10:52 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-01-18 10:52:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (71.20 KB, text/plain)
2010-09-05 11:46 UTC, Pavel Ondračka
no flags Details

Description Pavel Ondračka 2010-09-05 11:46:20 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: gimp-2.6 '/home/Paulie/Plocha/www/www-fotogalerie/2010-07-31 018.jpg'
component: gimp
crash_function: _g_utf8_normalize_wc
executable: /usr/bin/gimp-2.6
kernel: 2.6.35.4-12.fc14.i686
package: gimp-2:2.6.10-5.fc14
rating: 4
reason: Process /usr/bin/gimp-2.6 was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1283686983
uid: 500

Comment 1 Pavel Ondračka 2010-09-05 11:46:23 UTC
Created an attachment (id=443148)
File: backtrace

Comment 2 Pavel Ondračka 2010-09-05 11:48:17 UTC
How to reproduce:
1. open a jpeg file
2. make some changes
3. save

file is saved succesfully, however gimp crash

Comment 3 GoinEasy9 2010-09-19 02:09:57 UTC
Package: gimp-2:2.6.10-5.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Crash happened when I used the "Save as" function to save a screenshot that I had just scaled.
2.
3.


Comment
-----
Reproduced same error by using the "Save as" function a second time after restarting Gimp.

Comment 4 GoinEasy9 2010-09-19 02:18:38 UTC
I also got a Sig 11 from Nautilus at the same time, but can't reproduce the Nautilus Sig 11.  File was opened from Nautilus, right click, open with Gimp, nautilus was left open while I scaled the screenshot.  Then I used "Save as" to close graphic and Gimp Sig 11 happened.  I don't need Nautilus open to reproduce the Gimp Sig 11.

Comment 5 Nils Philippsen 2010-09-20 09:59:46 UTC
I can't reproduce this here. What language do you use on the desktop (output of the "locale" command). Please also post exact steps how to reproduce this (including file names, exact modifications done in gimp, etc.). Thanks.

Comment 6 GoinEasy9 2010-09-20 16:52:13 UTC
I use en-US on my desktop.  I thought comment #4 was pretty specific.  I created a screenshot with the screenshot app.  I believe it is saved as screenshot.png.  I loaded it into gimp, scaled it, then saved it.  When I scale in gimp, I do so slowly, i.e., 3840 resolution to 3000 to 2500 to 2000 etc., till i got to 800.  At that point I used the "Save as" function, where it successfully saved the file, but, also gave me a Signal 11.

Comment 7 Nils Philippsen 2010-09-21 10:45:00 UTC
I've finally managed to reproduce this, albeit not consistently -- sometimes it crashes, sometimes it doesn't. Here's what it took me to crash it:

1. "gimp Desktop/foo.png" <- screenshot image resized to 800x500 with ImageMagick's convert
2. Alt+I, then Esc to open the close the "Image" menu
3. Shift+Alt+S "Save As", some new file name
4. Lather, rinse, repeat

Comment 8 Nils Philippsen 2010-09-21 10:48:48 UTC
*... then close ...

Comment 9 Nils Philippsen 2010-09-21 11:04:30 UTC
Now this is weird:

When I ran this through VNC in a WindowMaker session, I couldn't provoke it to crash. When I ran this through VNC in a GNOME session, I could.

Comment 10 Nils Philippsen 2010-09-21 11:10:17 UTC
... and I only see this with GIMP running on F-14.

Comment 11 Nils Philippsen 2010-09-21 11:40:45 UTC
What desktop environment(s) do you use?

Comment 12 Pavel Ondračka 2010-09-21 13:01:08 UTC
(In reply to comment #11)
> What desktop environment(s) do you use?

I use GNOME.

Comment 13 Nils Philippsen 2010-09-21 15:03:09 UTC
Thanks for confirming this.

I'll change the component to gtk2 because the crash happens deep down in the stack according to the backtrace and it seems to be filtering the file name list (#2  0x03e7b7f5 in completion_match_func, #3  0x03e552eb in gtk_entry_completion_visible_func, #4  0x03fe09f8 in gtk_tree_model_filter_visible) when it's already in the process of deconstructing the file name text entry (#28 0x03e5577b in gtk_entry_completion_finalize, #31 0x03e510ef in gtk_entry_finalize, #32 0x03e7b701 in gtk_file_chooser_entry_finalize) while the whole dialog is brought down (#105 0x040439c9 in gtk_window_destroy).

I've made a few more tests. Summing things up:

- The most reliable way I found to provoke the issue is this:
  0. Have an image file "foo.png"
  1. "gimp foo.png"
  2. Shift+Ctrl+S -> "Save as": the file chooser dialog will be opened, "foo" of "foo.png" will be highlighted in the file name text entry
  3. Press "Arrow right" to place the cursor between "foo" and ".png", then type e.g. "-1" to give it a new name. Wait a bit after the dash (or other first character) to let the completion popup show itself.
  4a. Return to activate the file chooser dialog.
  4b. Return to activate the PNG saving options dialog.
  5. Poof.
  
- Contrary to what I speculated above, this doesn't seem to be related to any menu action.
- I could only reproduce this while running under GNOME, and only on F-14 (not F-13 or Rawhide/F-15).

Comment 14 GoinEasy9 2010-09-21 15:09:40 UTC
F14, Gnome.  And, as I test more, it is intermittent.  Using "Save" or "Save as" does work without crash.

Comment 15 Nils Philippsen 2010-09-21 15:21:15 UTC
NB: I could reproduce this with gedit as well, similarly with some slight modifications:

0. Have a text file "bar.txt"
1. "gedit bar.txt"
2. Shift+Ctrl+S
3. Arrow right, "Tab" to open the completion popup
4. Return
5. Poof.

Again, only on F-14.

Comment 16 Nils Philippsen 2010-09-21 15:22:23 UTC
(In reply to comment #14)
> F14, Gnome.  And, as I test more, it is intermittent.  Using "Save" or "Save
> as" does work without crash.

Using "Save" doesn't show the dialog. I guess for "Save As" to crash, it is important that the completion popup is shown -- step 3.

Comment 17 Nils Philippsen 2010-09-23 09:30:43 UTC
*** Bug 636648 has been marked as a duplicate of this bug. ***

Comment 18 Nils Philippsen 2010-09-27 08:33:57 UTC
*** Bug 637334 has been marked as a duplicate of this bug. ***

Comment 19 Nils Philippsen 2010-09-27 08:42:43 UTC
*** Bug 630362 has been marked as a duplicate of this bug. ***

Comment 20 GoinEasy9 2010-10-01 17:50:21 UTC
After last nights updates, I can't seem to reproduce this error any longer.

Comment 21 Christopher Beland 2010-10-05 14:10:32 UTC
Package: gimp-2:2.6.10-5.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
Crashed on "Save as..." after simply loading and cropping an image. It was successfully saved to disk before the crash.

Comment 22 Nils Philippsen 2011-01-27 09:41:10 UTC
*** Bug 672738 has been marked as a duplicate of this bug. ***

Comment 23 Nils Philippsen 2011-09-05 07:39:25 UTC
*** Bug 704655 has been marked as a duplicate of this bug. ***

Comment 24 Nils Philippsen 2012-01-18 10:52:46 UTC
Fedora 14 has reached its end of life. The same issue on Fedora 15 is tracked in bug #716325.

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


Note You need to log in before you can comment on or make changes to this bug.