After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 679265 - doesn't save/use JPEG quality settings after saving preferences
doesn't save/use JPEG quality settings after saving preferences
Status: RESOLVED DUPLICATE of bug 675981
Product: GIMP
Classification: Other
Component: User Interface
2.8.0
Other Linux
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2012-07-02 16:33 UTC by pauljohn
Modified: 2012-07-03 00:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description pauljohn 2012-07-02 16:33:44 UTC 
This did work in 2.6, so I figure you can make it work again.  

I want all JPEG files I export to have quality set at 95.  After using the Export option, I see toolbox options to set the percentage, I go to Gimp Preferences, ToolBox Options, and the button "Save Tool Options Now".  

In Gimp.2.8 on Debian "Testing", that has no apparent effect on quality of JPEG exports when other files are loaded.  If I do Export with new name, the quality seems always to be 90, while if I Export on same name, the quality setting is random between 80 and 100. Honestly, I can't detect any pattern in that situation. 

The saving of keyboard shortcuts does work in 2.8, that's why I think I understand how this is supposed to be done.
Comment 1 Alexandre Prokoudine 2012-07-02 16:40:00 UTC 
This bug has already been fixed in the stable 2.8 branch. The fix will be available in 2.8.1.
Comment 2 Michael Schumacher 2012-07-02 20:54:48 UTC 
In addition to the non-working save defaults part (that's fixed), the following behavior is intentional:

For images imported from JPEG files, the quality of the imported image is used when exporting, for images that haven't been exported yet, the default quality will be used.
Comment 3 Michael Schumacher 2012-07-03 00:02:04 UTC 
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.

*** This bug has been marked as a duplicate of bug 675981 ***