Bug 499507 - Very bright color on Ghostty only since 6.2.90
Summary: Very bright color on Ghostty only since 6.2.90
Status: RESOLVED DUPLICATE of bug 495647
Alias: None
Product: kwin
Classification: Plasma
Component: colour-management (show other bugs)
Version: 6.2.91
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-04 14:43 UTC by eifr
Modified: 2025-02-05 13:53 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
screenshot of ghostty (802.62 KB, image/png)
2025-02-04 14:43 UTC, eifr 		Details
GDK_DISABLE=color-mgmt ghostty (508.50 KB, image/png)
2025-02-04 16:06 UTC, eifr 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description eifr 2025-02-04 14:43:52 UTC 
Created attachment 177962 [details]
screenshot of ghostty

* See the attachmanet

the colors are very bright only since 6.2.90, did not happen on 6.2.5

STEPS TO REPRODUCE
1. install and run ghostty



EXPECTED RESULT
darker colors

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.12.12
KDE Plasma Version: 6.2.90 and 6.2.91
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1

ADDITIONAL INFORMATION
Comment 1 Vlad Zahorodnii 2025-02-04 15:42:29 UTC 
Can you try setting GDK_DISABLE=color-mgmt environment variable?
Comment 2 eifr 2025-02-04 16:05:32 UTC 
(In reply to Vlad Zahorodnii from comment #1)
> Can you try setting GDK_DISABLE=color-mgmt environment variable?

same, i added another attachment with log
Comment 3 eifr 2025-02-04 16:06:03 UTC 
Created attachment 177964 [details]
GDK_DISABLE=color-mgmt ghostty
Comment 4 Vlad Zahorodnii 2025-02-05 13:53:00 UTC 
Apparently, ghostty overwrites the GDK_DISABLE environment variable with its own whitelisted options (atm, there are only two options: gles-api and vulkan; color-mgmt is not one of those) if I'm reading the code correctly. Either way, it's an issue in GTK color management implementation. See also bug 495647

*** This bug has been marked as a duplicate of bug 495647 ***