After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 330138 - gimp seg faults after anchoring a pasted selection
gimp seg faults after anchoring a pasted selection
Status: RESOLVED OBSOLETE
Product: GIMP
Classification: Other
Component: General
2.2.x
Other All
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2006-02-06 15:59 UTC by Nils Philippsen
Modified: 2008-01-15 13:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gzipped stack trace (473.04 KB, application/octet-stream)
2006-02-13 20:48 UTC, Joel Uckelman
Details
stack trace, really this time (1.12 KB, text/plain)
2006-02-13 23:01 UTC, Joel Uckelman
Details

Description Nils Philippsen 2006-02-06 15:59:58 UTC
Steps to reproduce:
The relevant images as well as other details can be found in the corresponding
Fedora Core ticket https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=180077

1. Open PNG #1.
2. Select lower left corner with wand.
3. Copy the selection.
4. Open PNG #2.
5. Paste into the lower left corner there, and anchor the selection.
6. Save and close PNG #2.
7. Open PNG #3.
8. Paste into the lower left corner there, and anchor the selection.

Stack trace:


Other information:
Comment 1 weskaggs 2006-02-09 18:45:37 UTC
Does not seem to happen for cvs GIMP (with FC4/metacity).  A stack trace might be informative.
Comment 2 Joel Uckelman 2006-02-13 20:44:44 UTC
I'm attaching a stack trace now.
Comment 3 Joel Uckelman 2006-02-13 20:48:27 UTC
Created attachment 59289 [details]
gzipped stack trace
Comment 4 weskaggs 2006-02-13 22:42:58 UTC
Thanks, but that isn't a stack trace.  A stack trace is what you get by running in a debugger (i.e., "gdb gimp"), causing the program to crash, then typing "where" at the debugger prompt.
Comment 5 Joel Uckelman 2006-02-13 23:01:41 UTC
Created attachment 59299 [details]
stack trace, really this time

I feel silly. I only use a debugger several times a day, some weeks. I'm not sure why I gave you output from strace instead.
Comment 6 Sven Neumann 2006-02-14 07:18:37 UTC
The stack trace lacks some debugging symbols but from a quick look, I would say that the crash is in your GTK+ theme engine. The bug is almost definitely not in GIMP code. I would suggest that you try a different GTK+ theme and/or make sure you are using the latest version of GTK+.
Comment 7 Sven Neumann 2006-02-16 13:31:07 UTC
Setting status to NEEDINFO until Joel reports back.
Comment 8 Michael Schumacher 2006-02-20 20:35:24 UTC
Joel, please have a look at comment #6.
Comment 9 Joel Uckelman 2006-02-27 22:49:03 UTC
(In reply to comment #6)

I tried two other GTK+ themes, Traditional and Bluecurve, and found the same behavior with both. I'm using GTK+ 2.6.10, which I think is the most recent stable version, yes?
Comment 10 Michael Schumacher 2006-02-27 23:24:31 UTC
The latest stable GTK+ is 2.8.13. But if this is a general problem with GTK+, we would have had more reports already.
Comment 11 Joel Uckelman 2006-03-24 18:52:55 UTC
(In reply to comment #10)
> The latest stable GTK+ is 2.8.13. But if this is a general problem with GTK+,
> we would have had more reports already.
> 

I'm now using GTK+ 2.8.15, and the problem is gone.
Comment 12 André Klapper 2006-07-04 10:40:45 UTC
closing as per last comment, thanks for the feedback.