Erratic behavior on Ubuntu 10.04

[brianreumere]

So I installed fluxgui according to the instructions at http://stereopsis.com/flux/linux.html successfully. I killed the xflux binary that was running already and started the f.ux indicator applet from the GNOME Applications menu. I input my longitude and latitude, but my screen temperature did not change.

Using the Preview button seemed to change the temperature a little bit, but not completely. Opening the Preferences dialog from the notification area abruptly changes the color temperature to the desired nighttime setting, but only for a few seconds before changing back to the default color temp. The "current color temperature" in the preferences dialog seems to be all over the place as well, and doesn't seem to change in real-time.

As far as I can tell, running /usr/bin/xflux -z 00000 from the command line works fine. I'm not sure how to go about diagnosing this, but if there any specific tests to narrow down the problem please let me know.

[Kilian]

hmm, a couple of things here.

The preview button: Right now it doesn't work as expected, as it doesn't preview the selected color temperature (will release a fix soon) and apart from that it still doesn't seem to work completely, as a second request to preview does nothing/very little. I'll discuss that with Mike.

Regarding the other stuff, I should probably built in a --debug command line option that outputs everything to a log or stdout, that would make dealing with the other problems slightly easier.

Can you tell me the values of /apps/fluxgui/* in gconf?

[Otoris]

I'm getting the same issue. Preview acts real sketchy and I don't think it is dimming my screen properly, it looks like it gets stuck between 6500k and 2700k. All I entered was my zip, but today I tried entering Lat/Long and it actually went to the right setting for 3 seconds then blinded me with 6500k...

My gconf says, autostart 1 colortemp 0 latitude 33.2442813 longitude -86.8163773 zipcode 35114

[Otoris]

One more note, I was trying to get a game running in wine, and every time the game change my resolution in the NVidia control panel, the screen brightness would get messed up. Could this possibly conflict with the NVidia Drivers for Ubuntu 10.04 64-bit?

[brianreumere]

Sorry for the delay. This is what I have in /apps/fluxgui:

autostart 0 colortemp 1 latitude 41.557922 longitude -102.293701 zipcode 02111

[camilleacey]

any fix for this yet? f.lux works great on windows, not so good on my 10.04 ubuntu machine.

[kevinr]

I'm seeing this as well on Ubuntu 10.10. Every time I open up the indicator config dialog, it reports a different "current color temp", despite the screen brightness (usually) staying the same -- I wonder if communication between the xflux program and the dialog isn't screwed up somehow.

For the moment, running xflux by hand from the command line seems to work. I've added it to gnome-session-properties. I just don't get a useful settings dialog, and I have to go hunt the process down by hand when I want to turn it off temporarily.

[aquach]

The current color temperature and the preview stuff doesn't work very well from my experience with it, so I forked it here and changed it to instead display what the command line arguments for the current settings are. It should work better because every time the preferences window was shown, it would mess up the brightness when it asked for the current color temperature.

[Kilian]

it's a good solution, but you lose some functionality. We're working on a better solution without losing functionality :)

[aquach]

Yeah, I agree! I did what I could without being able to change xflux itself. After trying out the indicator applet for a bit, I realized the preferences window was messing with the way xflux was working because of the current color temperature readout, so I figured just taking it out until it was fixed was a better solution for now.

[ghost]

bump