eog's initial window height too small

[CKX]

Binary package hint: eog

Since hardy, opening an arbitrary image file with eog (Eye of GNOME) may bring up an initial window with an unsufficiant height.

As long as an image is smaller than eog's default window size, everything is fine and eog displays the image centered in its window.

But if an image is higher that eog's default window size, eog seems to miscalculate an appropriate height for its window to show the image completely in its original size. Even if there is enough screen space, eog opens a window that is too low so the image inside is scaled down to e.g. 98%.

At work, I often have to preview image files containing pixel graphics. It is important that they are shown unscaled. In feisty and gutsy, I used eog for this task because it started very fast and showed the images accurately. Unfortunately, starting with hardy, using eog makes things unconvenient. Each time I open eog, I have to manually drag the window bigger to see the image unscaled.

When eog starts, its initial window should at least be wide and high enough to show the selected image unscaled if possible.

[Pedro Villavicencio (pedro)]

thanks for your report, may you provide an screenshot? can you reproduce teh same with another user? are you using compiz or metacity? i recall a bug about compiz but its the opposite issue. thanks.

[CKX (chester-kollschen)]

I am using a recently installed Ubuntu/hardy (32-Bit) with metacity. The effect also occurs with a new user.

[Pedro Villavicencio (pedro)]

It looks like bug 238082

[CKX (chester-kollschen)]

I think the two bugs point out different issues.

My problem is that eog shows the initial image in a slightly too low window so that it is scaled down a bit. Which is not necessary since there is enough screen space available for the window to show up big enough for the image to be shown unscaled and complete.

So it's rather about eog's initial window sizing than its scaling behaviour.

[Pedro Villavicencio (pedro)]

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.