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 607274 - When No Color Profile is Detected, Ask Which One Should Be Assigned
When No Color Profile is Detected, Ask Which One Should Be Assigned
Status: RESOLVED OBSOLETE
Product: GIMP
Classification: Other
Component: User Interface
2.6.8
Other All
: Normal enhancement
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on: 608961
Blocks:
 
 
Reported: 2010-01-18 01:12 UTC by Frank Gore
Modified: 2015-10-21 21:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Frank Gore 2010-01-18 01:12:32 UTC 
Right now, when no color profile is detected in a file, Gimp just assigns it whatever working profile is currently set in the preferences. This is frustrating when I have Adobe RGB set as the working RGB profile, because any image I download from the web that doesn't have a color profile ends up over-saturated since its colorspace is incorrectly assigned as Adobe RGB.

A setting in the Color Management preferences along the lines of "Ask what to do when no profile is detected" or "Assume sRGB when no profile is detected" would go a long way towards fixing this problem. This is how many other applications do it, including Digikam and Photoshop.
Comment 1 Martin Ramshaw 2014-01-31 01:24:15 UTC 
I posted a patch to default the RGB profile when no profile is embedded to Bug 492048.

This will only work if the EXIF Interoperability Index is R03 or R98.
Comment 2 Michael Natterer 2015-10-21 21:57:04 UTC 
Git master always assumes sRGB when the file specifies no color space,
there is no "working space profile" any longer. The user can then
assign or convert to a profile as desired.