Bug 734037

SSIA, I got an abrt-generated report where the user described his issues in Portuguese, which I don't speak. It should tell users to report things in English (but I guess only if the interface isn't in English in the first place :-).

+++ This bug was initially created as a clone of Bug #722577 +++

abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 31354 bytes
cmdline: /usr/bin/gimp-2.6
component: gimp
Attached file: coredump, 220983296 bytes
crash_function: gimp_container_tree_view_drop_status
executable: /usr/bin/gimp-2.6
kernel: 2.6.35.13-92.fc14.i686
package: gimp-2:2.6.11-16.fc14
rating: 4
reason: Process /usr/bin/gimp-2.6 was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1310749927
uid: 500

How to reproduce
-----
1.Arrastei uma camada de um arquivo para a janela de um outro arquivo que estava aberto.

--- Additional comment from clauberload.br on 2011-07-15 13:29:30 EDT ---

Created attachment 513421 [details]
File: backtrace

--- Additional comment from nphilipp on 2011-08-10 11:45:16 EDT ---

Please describe in English what you did before GIMP crashed -- I don't understand Portuguese :-) -- and in more detail.

Google Translate gave me this translation: "I dragged a file to a layer of the window of another file was open." I interpreted this as:

- You had an image open in GIMP
- You dragged another image file from your file manager to the GIMP layers dialog of the first image, trying to add that new image as a layer
- GIMP crashed

I tried to reproduce this here (same GIMP package version, only for Fedora 15) and it worked for me as intended. Is what I did the same as what you did? Can you reproduce the problem? Please add any detail you can think of which is related to this crash. Thanks!

--- Additional comment from clauberload.br on 2011-08-27 13:36:42 EDT ---

(In reply to comment #2)

Sorry. But, the ABRT interface was in portuguese and i thought was to write too.

Yes. It's happened!

But now, i'm using Fedora 15 with Gimp 2.6.11 and now it's ok.

Thanks!

--- Additional comment from nphilipp on 2011-08-29 05:38:04 EDT ---

In that case I'll close this bug, thanks for clearing this up!