Bug 401051 - crop doesn't work
Summary: crop doesn't work
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: gthumb
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Behdad Esfahbod
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-27 15:09 UTC by Radek Vokál
Modified: 2008-10-10 21:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-10 20:14:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Radek Vokál 2007-11-27 15:09:22 UTC
Description of problem:
I've just updated Fedora 6 to Fedora 8 and the crop function in gthumb stopped
working. If you select view image -> image -> crop -> select some area -> apply 
.. nothing happens

Version-Release number of selected component (if applicable):
gthumb-2.10.7-1.fc8

How reproducible:
always

  
Actual results:
no cropping

Expected results:
cropped image

Additional info:
let me know what else I should provide

Comment 1 Michal Jaegermann 2008-10-09 20:48:58 UTC
I just bumped into the same problem with
gthumb-2.10.10-1.fc10.x86_64 and gthumb-2.10.8-3.fc9.

gthumb-2.10.8-3.fc9 is just "silent" while
gthumb-2.10.10-1.fc10.x86_64 opened from a terminal
produces a constant stream of messages like that:

(gthumb:3342): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated

This does not seem to be related to an inability to crop,
though.

This is nearly a year while this bug
remains as NEW.

Comment 2 Matthias Clasen 2008-10-10 20:12:11 UTC
It works somewhat unintuitively, but it works.

Use crop menuitem
Select area to crop to
Press Crop button
Press Save or Apply

Comment 3 Michal Jaegermann 2008-10-10 21:08:30 UTC
You are right but without your instructions I would
have trouble to realize that "Crop" is a button
and not just simply an operation marker.  Thanks!

Some "useability experts" obviously had a hand in this.


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