GNOME Bugzilla – Bug 792905
Color Balance settings persist across sessions and cannot be reset
Last modified: 2018-02-04 12:29:37 UTC
After modifying the color balance of any image, any changes you made in color balance will be remembered if you open the color balance option again, even after closing and opening GIMP again. Steps to reproduce: - open any image - Go to option Colors->Color Balance - Change the color balance of the image in a very noticeable way (for easy visual inspection) - Click OK to apply - Close GIMP - Open GIMP - Open the same image or a different one - Go back to option Colors-Color Balance BUG: At this point you should see the image preview start changing to the color balance you set previously even though the sliders are in their default position Expected results: Color balance should not remember the previous setting used. Reset range only resets the color balance to the already "remembered" color balance. System specs: Windows 10, Intel Core i3, 8GB RAM GNU Image Manipulation Program version 2.9.8 git-describe: GIMP_2_9_8 C compiler: Using built-in specs. COLLECT_GCC=x86_64-w64-mingw32-gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-w64-mingw32/6.3-win32/lto-wrapper Target: x86_64-w64-mingw32 Configured with: ../../src/configure --build=x86_64-linux-gnu --prefix=/usr --includedir='/usr/include' --mandir='/usr/share/man' --infodir='/usr/share/info' --sysconfdir=/etc --localstatedir=/var --disable-silent-rules --libdir='/usr/lib/x86_64-linux-gnu' --libexecdir='/usr/lib/x86_64-linux-gnu' --disable-maintainer-mode --disable-dependency-tracking --prefix=/usr --enable-shared --enable-static --disable-multilib --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --libdir=/usr/lib --enable-libstdcxx-time=yes --with-tune=generic --enable-version-specific-runtime-libs --enable-fully-dynamic-string --enable-libgomp --enable-languages=c,c++,fortran,objc,obj-c++ --enable-lto --with-plugin-ld --enable-threads=win32 --program-suffix=-win32 --program-prefix=x86_64-w64-mingw32- --target=x86_64-w64-mingw32 --with-as=/usr/bin/x86_64-w64-mingw32-as --with-ld=/usr/bin/x86_64-w64-mingw32-ld --enable-libatomic Thread model: win32 gcc version 6.3.0 20170415 (GCC) using GEGL version 0.3.25 (compiled against version 0.3.25) using GLib version 2.54.2 (compiled against version 2.54.2) using GdkPixbuf version 2.36.11 (compiled against version 2.36.11) using GTK+ version 2.24.31 (compiled against version 2.24.31) using Pango version 1.40.11 (compiled against version 1.40.11) using Fontconfig version 2.12.6 (compiled against version 2.12.6) using Cairo version 1.15.10 (compiled against version 1.15.10) (Type any character to close this window)
Let's mark this as a duplicate of the fix which caused this new behavior, and discuss solutions there instead of in two bugs... *** This bug has been marked as a duplicate of bug 792470 ***