| 2006-12-05 21:06:25 |
kko |
description |
If you display an image larger than your screen with imagemagick's 'display' command, you get a "Pan Ico" window where you can choose which portion of the image you want to have shown in the main window.
In the current version, the "Pan Ico" window will show a quadruple image instead of a single miniature image. What is curious is that if you close the "Pan Ico" window (from the X in the corner), a new one will immediately be spawned, and _in the new window, a single miniature image will correctly be shown_! Something in the creation of this "Pan Ico" window seems to not be initialised correctly.
I believe this regression was introduced with the very latest upgrade to imagemagick, although I can not be sure. Excerpt from dpkg.log:
/var/log/dpkg.log.1:2006-11-28 16:41:31 status installed imagemagick 6:6.2.4.5-0.6ubuntu0.4
Using Kubuntu Dapper LTS. |
Wow, this has got to be the strangest bug I have reported, though I've seen some obscure ones before...
If you display an image larger than your screen with imagemagick's 'display' command, you get a "Pan Ico" window where you can choose which portion of the image you want to have shown in the main window. In the current version, with only the "affected images" (defined below), the "Pan Ico" window will show a quadruple image instead of a single miniature image. If you close the "Pan Ico" window (from the X in the corner), a new one will immediately be spawned, and in that window, a single miniature image will correctly be shown.
After some diagnosis, among the files I tested, this bug _only_ happens with files (jpg) that have a vertical resolution of _exactly_ 3000 px. Not with 3008, not with slighly less, not with ones that have over 4000 px on the y axis... go figure. I have also tried to eliminate the possibility of the files having some other parameter besides the y resolution in common by resizing an other jpg file in Krita and saving it with 2998, 3000, and 3002 px... and rightly enough, the one with 3000 px exhibits this behaviour, and the others do not. ;-)
I first thought this was a regression with the very latest upgrade to imagemagick, but it has probably been this way since way back when, as it's a really isolated incident.
Using Kubuntu Dapper LTS, imagemagick 6:6.2.4.5-0.6ubuntu0.4. |
|
