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 637805 - Crop Tool Problem running GIMP 2.6.11 on XP Home
Crop Tool Problem running GIMP 2.6.11 on XP Home
Status: RESOLVED DUPLICATE of bug 606247
Product: GIMP
Classification: Other
Component: Tools
2.6.11
Other Windows
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2010-12-22 01:06 UTC by Joe
Modified: 2011-03-05 19:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Joe 2010-12-22 01:06:38 UTC 
Crop Tool Problem running GIMP1.6.11 on XP Home

A few weeks back my system crashed I I had to do a format and reload of my system. I run XP home and have loaded all available updates from Microsoft.
Prior I was running an earlier version of GIMP 2.6.? and the crop tool allowed me to change the aspect ratio. I have a project that when I crop and drag I like the ratio to be 1:2 so that for every 100 pixels in width I the box automatically drags to 200 pixels in height.
Since loading 2.6.11 when ever I try to set any aspect ratio the GIMP application crashes
 
"gimp-2.6.exe has encountered a problem and needs to close.  We are sorry for the inconvenience."
 
I reopen GIMP and the program works, the Crop tool works as long as I do not try to set any aspect ratio
 
Has anyone seem this problem?
 
Thanks
Comment 1 Michael Schumacher 2010-12-22 21:12:13 UTC 
Have a look at bug 606247 - we have no idea why this happens, and it does not happen - for whatever reason - to anyone who could investigate the problem further. Maybe you can provide the crucial clue?
Comment 2 Michael Schumacher 2011-03-05 19:48:44 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 bug 606247 ***