Redshift works fine outside of awesome, I've been using it for several
years.
I discovered the issue and resolved it. I had to replace the relative
path to the .redshift.conf with the absolute path.
The only edit I did was thus:
redshift.options = "-c /home/alex/.config/redshift.conf"
In the error log I has these messages:
fopen: No such file or directory
Unable to load config file.
It seems fairly odd that a relative path using tilde (~) leads to
errors, but the most likely explanation is that somewhere the
tilde-expansion fails.
Without going in-depth I'd guess the error comes at awful.util.spawn()
in the library. Maybe awful.util.spawn_with_shell() would work better?
On 02/28/2016 05:26 PM, fatemail1...@gmail.com wrote:
Does redshift work outside awesome, run it from console, with your
config, if it works, show log of the awesome when you trying to use
awesome-redshift
On Sun, Feb 28, 2016 at 05:18:03PM +0100, A M wrote:
Hello
I've setup redshift integration as described in these two links:
https://awesome.naquadah.org/wiki/Using_redshift_with_awesome
https://github.com/YoRyan/awesome-redshift/blob/master/README.md
I've followed the instructions carefully and imitated them precisely. As far
as I am aware of all dependencies are fulfilled (redshift and xrandr is
installed) .
I am getting no results at all. I've added the key-binding for
redshift.toggle and nothing happens when triggering it.
I'm using Fedora 23 with awesome 3.5.8 (Major Tom)
Should these instructions work with recent versions of awesome (they appear
to be a few years old)?
Is anyone else successfully using redshift?
How can I debug and determine the issue?
Best Regards
Alex
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
