GNOME Bugzilla – Bug 164158
Jpeg quality 0 incorrectly allowed
Last modified: 2008-01-15 12:45:31 UTC
In JPEG save dialog, the Quality parameter can be set to 0, which is an invalid value, and causes a "Bogus marker length" message in stderr.
0 is a valid setting for jpeg quality. I've tried saving a few jpegs with quality level 0, and they work without causing a "Bogus marker length". You'll need to provide more information, like the exact steps you do to reproduce the problem, and a sample image.
- open a file - choose "Save as..." - if the file name extension isn't .jpg, make it be - click Save - choose file quality setting 0 by either using the slider or by entering from keyboard (makes no difference which way you do that) - if "Show preview" is on, the preview isn't generated, and message "Bogus marker length" is output to the window where I started Gimp - if OK is then nonetheless clicked, the saving fails with "GIMP Message" window that says "Saving '/tmp/foo.jpg' failed: Plug-in could not save image", and another "Bogus marker length" message is shown I'm not sure what sample image you want, but this happens at least when original image is a PNG or a JPEG (created by several different programs), and the saved image can't be provided as saving fails. Trying to save This is on Fedora Core 3 with Gimp from gimp-2.2.2-0.fc3.2.i386.rpm. Libs are as following: libgimpwidgets-2.0.so.0 => /usr/lib/libgimpwidgets-2.0.so.0 (0x0087b000) libgimpcolor-2.0.so.0 => /usr/lib/libgimpcolor-2.0.so.0 (0x00291000) libgimpmodule-2.0.so.0 => /usr/lib/libgimpmodule-2.0.so.0 (0x00169000) libgimpbase-2.0.so.0 => /usr/lib/libgimpbase-2.0.so.0 (0x003b9000) libgimpthumb-2.0.so.0 => /usr/lib/libgimpthumb-2.0.so.0 (0x00bb9000) libgimpmath-2.0.so.0 => /usr/lib/libgimpmath-2.0.so.0 (0x00b4d000) libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x005aa000) libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x002a2000) libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x00111000) libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x00d23000) libm.so.6 => /lib/tls/libm.so.6 (0x00d8b000) libpangoxft-1.0.so.0 => /usr/lib/libpangoxft-1.0.so.0 (0x0012b000) libpangox-1.0.so.0 => /usr/lib/libpangox-1.0.so.0 (0x0033f000) libart_lgpl_2.so.2 => /usr/lib/libart_lgpl_2.so.2 (0x00206000) libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x00256000) libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x0021e000) libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x0016e000) libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x00130000) libdl.so.2 => /lib/libdl.so.2 (0x00133000) libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x003c6000) libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00cbb000) libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00c31000) libz.so.1 => /usr/lib/libz.so.1 (0x00beb000) libpthread.so.0 => /lib/tls/libpthread.so.0 (0x001b7000) libc.so.6 => /lib/tls/libc.so.6 (0x00441000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x0095b000) libXrandr.so.2 => /usr/X11R6/lib/libXrandr.so.2 (0x00137000) libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x0013a000) libXinerama.so.1 => /usr/X11R6/lib/libXinerama.so.1 (0x00142000) libXft.so.2 => /usr/X11R6/lib/libXft.so.2 (0x00145000) libXcursor.so.1 => /usr/X11R6/lib/libXcursor.so.1 (0x00157000) libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x00160000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x001c9000) /lib/ld-linux.so.2 (0x00593000) libexpat.so.0 => /usr/lib/libexpat.so.0 (0x00c9a000)
T
Oops, made a bogus comment above by mistake. This is caused by a buggy patch in the fedora RPM (which was trying to fix bug #164087).