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 587857 - Desaturate on coppied layer causes crash
Desaturate on coppied layer causes crash
Status: RESOLVED DUPLICATE of bug 577581
Product: GIMP
Classification: Other
Component: Tools
2.6.6
Other All
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2009-07-06 07:36 UTC by karl ward
Modified: 2009-07-09 20:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description karl ward 2009-07-06 07:36:51 UTC
Steps to reproduce:
1. open up image
2. Duplicate Background layer
3. desaturate backround copy and gimp crashes


Stack trace:


Other information:
Comment 1 Michael Schumacher 2009-07-06 09:39:16 UTC
I can't reproduce this. As there are many way to do the actions you describe, please add more details.
Comment 2 Sven Neumann 2009-07-06 20:00:19 UTC
Isn't this just another duplicate of the "Colors tools crash 2.6.6 on Windows" bug?
Comment 3 karl ward 2009-07-06 21:06:25 UTC
Looking at the other bugs I beleive it could be, sorry I did check to see if a similer bug was logged but seemed to have missed it
Comment 4 Michael Schumacher 2009-07-08 11:00:46 UTC
You should tell us if this could be a duplicate of bug #577581 - you didn't tell us anything about your system yet, for example.
Comment 5 karl ward 2009-07-08 18:39:26 UTC
I am using Vista Sp1 to start with gimp seemed to have no problems then all of a problem it started to crash whenever i tried to desaturate, I tried re-installing and again it would work for a while, I then went back to 2.6.5 and everything wasw working fine with that so i tried again with 2.6.6 and at the moment am not getting an error
Comment 6 Michael Schumacher 2009-07-09 20:17:50 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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