@lorna
USING MACOS VENTURA M1 - 16".
IT DOES KEEP HAPPENING TO ME;
IT'S LIKE F.LUX DOESN'T KNOW WHAT'S F.S. OR NOT.
AND APPS DO NOT APPEAR IN THE LIST OF RECOGNIZED.
ON WINDOWS YOUTUBE GOING FULLSCREEN IS CONSIDERED AN APP THAT'S FULLSCREEN, NOT "CHROME". I'D LIKE THAT.

@Lorita f.lux has a feature to disable for certain apps. So while you're running Chrome check the f.lux "Disable" menu to see if that's what is going on.

@herf @ngolderm thank you both :-)

@anewoman on some Macs, the f.lux icon will be hidden when using an app with too large a menu. If you switch to a different app, it should appear again.

It could also just be that f.lux is not running, so find the icon in Finder and run it again to be sure.

https://justgetflux.com/news/pages/macquickstart/

@herf I'm unable to bring up f.;ux at all. I can be on this forum, but I'm unable to find a way to set it at all.

Had this same problem. Solved by moving the application to my Applications folder and running it from there. I was running it from my Downloads folder.

Still not working after v42.1 update.Screen Shot 2022-12-03 at 2.05.21 AM.png

Has anyone tried disabling the profile writer? Go to Terminal and type:

defaults write org.herf.Flux disableProfile 1

Then go to system prefs > displays and make sure to delete (or deselect) the f.lux profile if there is one.

I have this weird issue with f.lux and just one app (my IDE).
I recorded it in youtube video https://www.youtube.com/watch?v=l6HZXV3whCY

f.lux 42.1

IntelliJ IDEA 2022.2.3 (Ultimate Edition)
Build #IU-222.4345.14, built on October 5, 2022
Runtime version: 17.0.4.1+7-b469.62 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 12.6
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 12
Metal Rendering is ON
Non-Bundled Plugins:
com.wakatime.intellij.plugin (14.1.1)
com.jetbrains.darkPurpleTheme (1.3)
com.intellij.plugins.netbeanskeymap (222.4345.15)
com.dmarcotte.handlebars (222.4345.14)
com.jetbrains.plugins.meteor (222.4345.14)
cn.yiiguxing.plugin.translate (3.3.5)

@herf
Just updated to MacOS 12.6.1 but had this problem before; applied the fix and removed it via your instructions and voila -- everything works!


Thanks.