=====I have found a solution to the screen flickering===== With chrome or opera, install the extension h264ify. This works for me to end the flickering. Not sure about Firefox. I had to register just for this post because it's so sad to see you guys flounder without a real solution. Best,

Flux 4.33 beta, windows 7 x64. Can't get tray icon to front. "Control Panel\All Control Panel Items\Notification Area Icons" - show all icons is unchecked. When I set "Show icon and notifications" for flux, every time computer is restarted there is new entry for flux and tray icon is hidden. I removed /nohide from executable but this brings flux window to front, not tray icon.

here the picture links since embedding didn't work: https://www.dropbox.com/s/f1mu1azacaohefp/Screenshot 2017-02-21 23.30.39.png?dl=0 https://www.dropbox.com/s/x3cyex5yr50e0ry/Screenshot 2017-02-21 23.32.06.png?dl=0 Also I haven't noticed the problem when playing a video file with VLC or similar -- just from streaming.

My 5cents, disabling the auto brightness adjustment didn't help my issue. What helped in my case is that I replaced the cable of the monitor. lightning to D-SUB adapter with a D-SUB cable connected to the monitor -> constant screen refreshing waving/flickering effect (strangely only when flux enabled and color is warm) HDMI -> DVI cable connected to the monitor - No flickering I tried with 2 different monitors and I had the same issue / effect / resolution one LG and one Samsung. (Simply changing the D-SUB cable to another D-SUB didn't help, using another Lightning socket or adapter didn't help either)

@herf Thank youuuu!!

Had a crash this morning. Machine was up, I could SSH to it, but the screen was dark and flickering. Rebooted and checked the system.log. This may be a GPU failure issue, but I figured I would throw this in for those with similar errors and a LOT of Flux messages, but the more I dug the more it seemed like the issue was my GPU and not Flux. Oct 25 08:04:05 max kernel[0]: IOVendorGLContext::ReportGPURestart Oct 25 11:49:04 max watchdogd[402]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive Oct 25 11:49:05 max watchdogd[402]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - failed to gather a spindump for (com.apple.WindowServer) Oct 25 11:05:10 max kernel[0]: NVDA(OpenGL): Channel timeout! Oct 25 11:05:35 max kernel[0]: NVDA(OpenGL): Channel timeout! Oct 25 11:06:21 --- last message repeated 1 time --- Oct 25 11:06:21 max kernel[0]: NVDA(OpenGL): Channel timeout! Oct 25 11:06:41 max kernel[0]: NVDA(OpenGL): Channel timeout! [... above repeated several times, then ... ] Oct 25 11:49:05 max Dock[360]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0xfffffecc: (ipc/mig) server died Oct 25 11:49:05 max Upwork[341]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0xfffffecc: (ipc/mig) server died Oct 25 11:49:05 max Flux[951]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0xfffffecc: (ipc/mig) server died Oct 25 11:49:05 max Google Chrome[333]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0xfffffecc: (ipc/mig) server died Oct 25 11:49:05 max Upwork[341]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port Oct 25 11:49:05 max Flux[951]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port Oct 25 11:49:05 max GPGSuite_Updater[1355]: Set a breakpoint at CGSLogError to catch errors as they are logged. Oct 25 11:49:05 max CalNCService[383]: Set a breakpoint at CGSLogError to catch errors as they are logged. Oct 25 11:49:05 max Upwork[341]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port Oct 25 11:49:05 max SystemUIServer[362]: HIToolbox: received notification of WindowServer event port death. [... later, Flux repeating every few seconds ...] Oct 25 11:51:04 max Flux[951]: Empty gamma size Oct 25 11:51:04 max Flux[951]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port Early 2008 Mac Pro, 18GB RAM OS X 10.11.6 NVIDIA GeForce 8800 GT 512 MB F.lux 37.7 I've now updated my NVIDIA card with their drivers, maybe it is a GPU issue and not a Flux issue. Wait and see FTW!

Sure @herf, here is what is shown: Intel Corporation 27.20.100.9126: Intel(R) Iris(R) Xe Graphics (20201223) Generic PnP Monitor, 309 x 174mm, built 2019 Chromaticities: R=0.589844 0.349609 G=0.330078 0.554688 B=0.153320 0.119141 W=0.313477 0.329102 sRGB gamut: 63%, AdobeRGB gamut: 40% Unlimited gamma ramp=1, Internal ramp=0 Monitor 1 on Intel(R) Iris(R) Xe Graphics Has VCGT profile=0, Gamma Ramp works=1 Windows Build: 19043.1110

@A-Former-User said in Windows 10 May update (1903): As a followup, the following made my DisplayLink external monitor work with f.lux again: (1) Upgrade the DisplayLink drivers to the latest stable. --> https://www.displaylink.com/downloads/windows (2) Set enableGammaRamp to true using regedit. --> https://www.displaylink.org/forum/showthread.php?p=82958#post82958 Rajiv I figured it would be a good feedback to back up that post, and also to update the links. So if you have TINTED SCREENSHOTS with DISPLAYLINK adapters (like my Dell D6000) using ShareX or other snipping tool... try the following steps to resolve the issue: (1) Upgrade you DisplayLink adapter to the latest version (10.1.2875.0 as of today): https://www.synaptics.com/products/displaylink-graphics/downloads/windows (2) Enable nigh light with registry setting: https://support.displaylink.com/knowledgebase/articles/1886413-how-to-enable-night-light-or-f-lux-on-displaylink For point (2), there is actually an alternative that doesn't require messing up with the registry by enabling Night Light using the UI of the DisplayLink Manager: https://www.microsoft.com/en-us/p/displaylink-manager/9n09f8v8fs02 My drive info's: DisplayLink 10.1.2875.0: DisplayLink USB Device (20210811) Intel Corporation 27.20.100.9126: Intel(R) UHD Graphics 620 (20201223) DisplayLink 10.1.2875.0: DisplayLink USB Device (20210811) Generic PnP Monitor, 344 x 194mm, built 2019 Chromaticities: R=0.584961 0.363281 G=0.349609 0.567383 B=0.162109 0.123047 W=0.312500 0.328125 sRGB gamut: 61%, AdobeRGB gamut: 39% Generic PnP Monitor, 708 x 399mm, built 2019 Chromaticities: R=0.678711 0.313477 G=0.200195 0.721680 B=0.151367 0.045898 W=0.298828 0.317383 sRGB gamut: 102%, AdobeRGB gamut: 100% Unlimited gamma ramp=1, Internal ramp=0 Monitor 1 on Intel(R) UHD Graphics 620 Has VCGT profile=0, Gamma Ramp works=1 Monitor 2 on DisplayLink USB Device Has VCGT profile=0, Gamma Ramp works=1 Windows Build: 19042.1237 Thanks for the forum that helped me resolve my issue. Mat

@Tungsten_smooth said: @Gentz Now you can open the magnifier and invert the colors (ctrl alt i). I think it's the APU not understanding the color inversion part. Yeah, something somewhere is definitely not allowing f.lux to work correctly. :/

@User_V1 Reinstalling via Windows solved my issue, thanks alot for the compilation, youre my hero of the day :3!

Thank you Elhem! I will give that a shot.

@dsw2222 said in "Sorry, we only support 8 and 10-bit displays right now.": #!/bin/bash /usr/bin/xflux11 -r 0 $* you can go further and do this the elegant debian way create the script as /usr/local/bin/xflux and make it executable copy the xflux12 binary as /usr/local/bin/xflux12 and make it executable run this once: update-alternatives --install /usr/bin/xflux xflux /usr/local/bin/xflux 100

Sadly vers. 4.100 didn't do anything either ;-(

@TwoCables said in UWP f.lux: Also, as you can see from the update page, it says "These pages are popping up too early for Windows App Store users. Sorry, we’re working on a fix!" Sorry, I totally missed that! It's good information to know! I will probably just stick to Windows App in this case since developers know about the issue :-) Thank you for the very quick reply!