Red Hat Bugzilla – Bug 187663
gthumb doesn't respect resize preference in fullscreen
Last modified: 2008-08-02 19:40:36 EDT
Description of problem:
Previously (fc4) gthumb would resize images smaller than the screen when set to
in preferences (Viewer-> After loading an image: Fit image to window)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Set preference to Fit image to window
2.View small image in fullscreen (press v)
Images retains original size, does not get resized up to fullscreen. (larger
images will be shrunk though)
It will be resized to larger than original size if you maximize the window but
not in fullscreen view.
Images smaller than screen should be upscaled.
Also reported in upstream bugzilla:
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
I imagine this bug could be closed. The upstream bug was resolved with a patch
that brought back the old behaviour only partly. I don't use it anymore.
(In reply to comment #3)
> I imagine this bug could be closed. The upstream bug was resolved with a patch
> that brought back the old behaviour only partly. I don't use it anymore.
Thanks for reporting. I'm closing this issue as it is resolved.