Legacy ImageMagick Discussions Archive

I run imagemagick v5 and v6 within Ubuntu 16.04. The problem I have come across is that when I run the chop function within the "display" GUI, I cannot actually select the region to be chopped. What happens is that as soon as I carry out the first click within the image (which should select the start of the region to be chopped), this click is being read as the *second* click, i.e. the location is interpreted as the end of the region to be chopped, with the beginning always defaulting to the top left corner. So this means I am only able to chop region starting from the top left corner.

Quite a lot of views, but no replies so far. Does this mean that I'm the only one having this problem or just that nobody knows how to solve this? It would be nice if somebody else running ubuntu 16.04 could let me know if it's just me.

Click and hold. Move your mouse while holding. Do you get a line between the first click and the current location of the pointer? If so, you're chopping properly. Perhaps there is a more intuitive way to chop, but the way it works now does chop for us.

Thanks, but that's what I'm doing.

The issue is that immediately after the first click the line that appears is anchored at the top left. I.e. effectively it's as if the first click had happened at the top left. I've been using the chop function happily for years -- I've only encountered this issue recently. Not 100% if it's related to upgrading to 16.04 or not, but it's somewhere around that time that I noticed.

The issue is that immediately after the first click

Just to be clear, when you say "click", did you press down and hold without letting up on the mouse and then drag before letting up?

The chop function utilizes the X11 library. The ImageMagick code for chop has not changed in over 10 years. Given that, perhaps there has been bug introduced in X11. Unfortunately, we can not reproduce the problem so we have no path to test or fix the problem. We're using Fedora and CentOS for our testing.

I have exactly the same problem with Ubuntu 16.04 so I think it's problem with some changes in Ubuntu