-
Notifications
You must be signed in to change notification settings - Fork 177
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
f.lux not working anymore on ubuntu-16.04 #129
Comments
I installed f.lux recently. But I didn't see any difference on the screen before and after the installation. seems like f.lux not working on the Ubuntu-16.04. Please revert back here if anyone got it working on Ubuntu-16.04. |
did you run flux? it wont start automatically on install |
Yes I run it.
…On Sat, 2 Nov, 2019, 10:50 AM ENigma, ***@***.***> wrote:
did you run flux? it wont start automatically on install
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#129?email_source=notifications&email_token=ADJROICGH2254RYJOO3CT4DQRUE2TA5CNFSM4JCTGJXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC4UF5A#issuecomment-549012212>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADJROIE3NDT7ZERQMMXOTS3QRUE2TANCNFSM4JCTGJXA>
.
|
I got the same problem on Ubuntu 19.04 disco (x86-64) |
The reboot didn't fix. It's definitly not working for me neither. |
It won't work for Ubuntu-16.04 or greater. I switched to redshift. Follow the article from here: https://linoxide.com/tools/install-use-redshift-ubuntu-16-04/ |
Alright, I will try it. Thank you ! |
FWIW - working on Kubuntu 19.04 |
I have the same issue on 16.04. When running from terminal I get the following assertion error when I try to preview the color: |
Duplicate of #27 |
Before opening a new issue for a bug, please:
Check that you're not experiencing an existing issue. In particular, Issue #27 is very common.
Install
xflux-gui
from source if you used the PPA and the PPA is stale. This is easy to do and ensures your issue isn't already fixed.Thanks!
The text was updated successfully, but these errors were encountered: