Bug 783861 - gthumb won't show fullsize image.
Summary: gthumb won't show fullsize image.
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: gthumb
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christian Krause
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-23 00:12 UTC by Dave Jones
Modified: 2015-01-04 22:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-14 21:48:16 UTC
Type: ---


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 666302 0 None None None Never

Description Dave Jones 2012-01-23 00:12:07 UTC
gthumb used to be my preferred way to browse a directory of photos.
Now, when I try to view a picture fullsize by double clicking it, it just shows me the thumbnail. Even clicking 'fullscreen' just shows the thumbnail.

Comment 1 Christian Krause 2012-01-29 23:43:29 UTC
It looks like that there is an issue updating from 2.12.x to 2.14.x: the settings seem to be wrongly imported/migrated so that all extensions are disabled by default.

There is already an upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=666302 

Although I have seen the same issue I can't reproduce it.


To help to debug the issue, please can you retrieve all your gthumb settings via

gconftool-2 -R /apps/gthumb

and attach them to this bug report.

To re-enable your extensions, just use the config dialog in gthumb:

Edit -> Preferences -> Extensions

and re-enable the ones you need. If the pictures are still not shown full-screen, you can check

Edit -> Preferences -> Viewer -> After loading an image

This should be set to "Fit to Window" for fullscreen display.

Comment 2 Dave Jones 2012-01-31 17:27:13 UTC
the key was that no extensions were enabled.
(In previous releases that wasn't necessary for 'basic viewing'. When I turned that on, it behaves as expected.


Note You need to log in before you can comment on or make changes to this bug.