Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Color Mode Configuration Protection might not take effect on app startup #3730

Open
V4N089 opened this issue Dec 2, 2024 · 7 comments
Open
Assignees
Labels
bug Something isn't working done All tasks are completed internal pre-release Enable internal pre-releases under Settings/Applications/Updates
Milestone

Comments

@V4N089
Copy link

V4N089 commented Dec 2, 2024

Hi,
Seems like after the last update Color mode and its Configuration protection option don't work anymore at startup.
If I change it manually it sticks even if I enable/disable HDR or the Mac goes in&out of standby.
I've added 2 screenshots taken just after logging in, as you can see Protection is enabled and should force 10bit RGB but in reality color mode is YCbCr 10bit

  • Mac mini M4 running Sequoia 15.1.1
  • Samsung G85SB
  • App ver. 3.2.1 Build 35753

Thanks!

Screenshot 2024-12-02 alle 01 32 04
Screenshot 2024-12-02 alle 01 31 53

@V4N089 V4N089 changed the title Color mode & Configuration Protection don't work anymore at startup Color mode doesn't work anymore at startup, even with Configuration Protection enabled Dec 2, 2024
@waydabber waydabber added the investigating Investigating issue label Dec 2, 2024
@waydabber waydabber changed the title Color mode doesn't work anymore at startup, even with Configuration Protection enabled Color Mode Configuration Protection does not take effect on app startup Dec 2, 2024
@waydabber
Copy link
Owner

So to rephrase the issue, Color Mode change generally works and Config Protection works when the app is already running and the mode needs to be enforced - but on app startup the protection is not enforced.

@V4N089
Copy link
Author

V4N089 commented Dec 2, 2024

So to rephrase the issue, Color Mode change generally works and Config Protection works when the app is already running and the mode needs to be enforced - but on app startup the protection is not enforced.

Yep exactly! Sorry my english is crap 😅

Before the last update just after writing my password at login and before getting to the desktop I used to get a monitor blackout (just like when I manually change color mode from the app) but not anymore

@waydabber waydabber self-assigned this Dec 2, 2024
@waydabber waydabber changed the title Color Mode Configuration Protection does not take effect on app startup Color Mode Configuration Protection might not take effect on app startup Dec 2, 2024
@waydabber waydabber added bug Something isn't working done All tasks are completed unreleased Still baking in the oven and removed investigating Investigating issue labels Dec 2, 2024
@waydabber waydabber added this to the v3.2.2 milestone Dec 2, 2024
@waydabber
Copy link
Owner

waydabber commented Dec 2, 2024

Ok, the issue is a bit tricky as it sometimes work, other times it does not. This is due to a timing issue with Paddle checking Pro features on startup (it's a bit slow after a reboot or when the app was not started for a while). Concig Protection is a Pro dependent feature and if Pro is not yet activated, the app skips enforcement and then does not do it after the license is validated.

@waydabber waydabber added internal pre-release Enable internal pre-releases under Settings/Applications/Updates and removed unreleased Still baking in the oven labels Dec 2, 2024
@V4N089
Copy link
Author

V4N089 commented Dec 2, 2024

Thanks for the explanation! There’s something I can do my side to make it work again? The app is set to load at startup already

@waydabber
Copy link
Owner

Yes, you should enable Applications/Updates/Pre release + Internal pre-release. Hopefully the update fixes the issue. Let me know if it doesn't!

@V4N089
Copy link
Author

V4N089 commented Dec 2, 2024

Yes, you should enable Applications/Updates/Pre release + Internal pre-release. Hopefully the update fixes the issue. Let me know if it doesn't!

Just updated to internal pre-release as you said and it's working! Thanks a lot waydabber, much appreciated 😉

@waydabber
Copy link
Owner

Nice! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working done All tasks are completed internal pre-release Enable internal pre-releases under Settings/Applications/Updates
Projects
None yet
Development

No branches or pull requests

2 participants