https://bugs.kde.org/show_bug.cgi?id=515052
Dmitry Kazakov <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|ASSIGNED |RESOLVED Latest Commit| |https://invent.kde.org/grap | |hics/krita/-/commit/601e40f | |7244bd69d646e09143bee571b88 | |96073e --- Comment #13 from Dmitry Kazakov <[email protected]> --- Git commit 601e40f7244bd69d646e09143bee571b8896073e by Dmitry Kazakov. Committed on 29/01/2026 at 12:15. Pushed by dkazakov into branch 'master'. Fall back to unmanaged mode when Wayland reports nonsense It seems like hyprland compositor is okay with sending us nonsense instead of the preferred surface description: wp_image_description_info_v1#42.primaries(0, 0, 0, 0, 0, 0, 0, 0) wp_image_description_info_v1#42.tf_power(10000) wp_image_description_info_v1#42.tf_named(2) wp_image_description_info_v1#42.luminances(2000, 80, 80) wp_image_description_info_v1#42.target_primaries(0, 0, 0, 0, 0, 0, 0, 0) wp_image_description_info_v1#42.target_luminance(0, 0) wp_image_description_info_v1#42.target_max_cll(0) wp_image_description_info_v1#42.target_max_fall(0) wp_image_description_info_v1#42.done() Obviously, LCMS cannot create a profile with zero primaries, so we should gracefully report the profile creation failure and continue with different options (just downgrade color management). When everything has failed, we just add an "ERROR" message to the color management report (though it is quite improbable to happen). M +174 -137 libs/ui/KisCanvasSurfaceColorSpaceManager.cpp M +6 -0 libs/ui/KisCanvasSurfaceColorSpaceManager.h M +8 -1 plugins/color/lcms2engine/colorprofiles/IccColorProfile.cpp https://invent.kde.org/graphics/krita/-/commit/601e40f7244bd69d646e09143bee571b8896073e -- You are receiving this mail because: You are watching all bug changes.
