[GH-ISSUE #692] Detect apps which manipulate gamma tables and display a warning #464

New issue

Closed

opened 2026-05-05 06:03:57 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 06:03:57 -06:00

Owner

Originally created by @the0neyouseek on GitHub (Oct 9, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/692

Originally assigned to: @waydabber on GitHub.

Before opening the issue, have you...?

Searched for existing issues

When using both MonitorControl and apps that use gamma table manipulations like f.lux issues can arise. Theses issues can be fixed by disabling either settings in MonitorControl or simply quitting the other app.

Describe the solution you'd like

We could use urlForApplication(withBundleIdentifier:) to detect the installation of a list of apps (using their bundle id) and display a warning to the user about this issue.

The warning could look something like this :

Gamma table app detected
Hey! It looks likes you're using `<app>`, nothing wrong here but MonitorControl and `<app>` both use gamma table manipulation and can't do this at the same time, causing issue in both apps. If you'd like, you can disable gamma table manipulation in MonitorControl
Disable gamma table manipulations	Leave gamma table on

Describe alternatives you've considered

We could also disable gamma table manipulations by default, but I don't think that would be ideal

Anything else?

No response

Originally created by @the0neyouseek on GitHub (Oct 9, 2021). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/692 Originally assigned to: @waydabber on GitHub. ### Before opening the issue, have you...? - [X] Searched for existing issues ### Is your feature request related to a problem? Please describe When using both MonitorControl and apps that use gamma table manipulations like `f.lux` issues can arise. Theses issues can be fixed by disabling either settings in MonitorControl or simply quitting the other app. ### Describe the solution you'd like We could use [`urlForApplication(withBundleIdentifier:)`](https://developer.apple.com/documentation/appkit/nsworkspace/1534053-urlforapplication) to detect the installation of a list of apps (using their bundle id) and display a warning to the user about this issue. The warning could look something like this : <table> <thead> <tr> <th colspan=2>Gamma table app detected</th> </tr> </thead> <tbody> <tr> <td colspan=2>Hey! It looks likes you're using <code><app></code>, nothing wrong here but MonitorControl and <code><app></code> both use gamma table manipulation and can't do this at the same time, causing issue in both apps. If you'd like, you can disable gamma table manipulation in MonitorControl</td> </tr> <tr> <td>Disable gamma table manipulations</td> <td>Leave gamma table on</td> </tr> </tbody> </table> ### Describe alternatives you've considered We could also disable gamma table manipulations by default, but I don't think that would be ideal ### Anything else? _No response_

gitea-mirror

2026-05-05 06:03:57 -06:00

closed this issue
added the
enhancement

done
labels

gitea-mirror commented

2026-05-05 06:04:04 -06:00

Author

Owner

@waydabber commented on GitHub (Oct 9, 2021):

Yes, f.lux compatibility seems to be a recurring issue. We can also solve this by checking periodically whether gammatable changes persist (there is already a job in MC that mostly does brightness syncing, it could be easily added there). If it doesn't, then we can pop a notification. This could work for any other apps as well (for example running Lunar and MC side by side is also not ideal).

@waydabber commented on GitHub (Oct 9, 2021): Yes, f.lux compatibility seems to be a recurring issue. We can also solve this by checking periodically whether gammatable changes persist (there is already a job in MC that mostly does brightness syncing, it could be easily added there). If it doesn't, then we can pop a notification. This could work for any other apps as well (for example running Lunar and MC side by side is also not ideal).

gitea-mirror commented

2026-05-05 06:04:10 -06:00

Author

Owner

@waydabber commented on GitHub (Oct 9, 2021):

Since in 4.0.0 gamma manipulation is enabled by default, I think we should not do a release without incorporating this solved as this seems to be a widespread issue.

@waydabber commented on GitHub (Oct 9, 2021): Since in 4.0.0 gamma manipulation is enabled by default, I think we should not do a release without incorporating this solved as this seems to be a widespread issue.