https://bugs.kde.org/show_bug.cgi?id=515402
Rynn <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |REOPENED Ever confirmed|0 |1 --- Comment #3 from Rynn <[email protected]> --- Just to make it clear, the observed 2.2 gamma is as visible as it can be after loading the profile, in a browser, in Dolphin, not just in DisplayCAL. I just wanted hardware confirmation, in order not to get told that my eyes are the issue; and I had DisplayCAL installed also on Linux. If you load an .icc, the whole point is to *correct* the output, otherwise, say this scenario: if I manually misconfigure my monitor to a dark 2.6 gamma, KWin doesn't auto-magically correct it to 2.2 on its own, it needs an ICC profile. But when I provide that profile, KWin ignores the 2.4/2.6 curve inside it and just 'assumes' 2.2 anyway. You're essentially saying KWin only supports profiles that don't actually change anything. If a profile's job is to correct the output to a target, and KWin refuses to apply that correction, then the implementation is broken by design. -- You are receiving this mail because: You are watching all bug changes.
