-
Notifications
You must be signed in to change notification settings - Fork 423
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
redshift-gtk doesn't read conf files at log-in #870
Comments
PolGZ
changed the title
It doesn't read conf files at boot
It doesn't read conf files at log-in
Sep 1, 2022
PolGZ
changed the title
It doesn't read conf files at log-in
redshift-gtk doesn't read conf files at log-in
Sep 1, 2022
This is most likely because the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have checked the FAQ and open issues, and I don't think my issue is exactly mentioned there, since it is not because I'm using the
~/.config/redshift/redshift.conf
path.redshift-gtk -c ~/.config/redshift.conf
it works fine~/.config/autostart
(usingdex
) it says "no such file or directory, unable to load the file"Here is my
.desktop
file:Expected behavior
Being able to load it at start using
dex
as any of my other autostart .desktop files.dex -a -s /etc/xdg/autostart/:~/.config/autostart/
Error output/logs/screenshots
error.png
Software versions (please complete the following information):
apt
Others
If you are wondering why I don't just run it from my bspwmrc it is because it creates by default a
redshift-gkt.desktop
file when it launches, so next time I restart my WM or log-out&back in, I get the error again.For now I commented out the "Exec=" line on the desktop file, so it doesn't create another one and it runs just from my window manager startup programs, but since it creates a autostart entry on its own, I would like to know why it can't read the file, and I would like to use it, so I also get it on other WMs and x11 DEs from that autostart .desktop file.
The text was updated successfully, but these errors were encountered: