maoserr / redshiftgui

Monitor color temperature adjustment tool
http://maoserr.github.io/projects/redshiftgui/
GNU General Public License v3.0
231 stars 28 forks source link

Error reading lightmap #13

Closed ghost closed 1 year ago

ghost commented 9 years ago

This standard line "map=177.00|100.00;3.00|100.00;-6.00|0.00;-174.00|0.00;" triggers this error:

PM:[opt_parse_map] Map empty.

removing the line fixes the issue.

issue exist on manjaro xfce 32/64bit running as both root/user

ghost commented 8 years ago

I'm having the same issue, it refuses to startup. Did not test the suggest fix.

dileepmani commented 8 years ago

change this line "map=177.00|100.00;3.00|100.00;-6.00|0.00;-174.00|0.00;" to "map=177.00,100.00;3.00,100.00;-6.00,0.00;-174.00,0.00;" (i.e replace | with ,) in .redshiftgrc in home folder and save it.

ghost commented 8 years ago

I can confirm the suggested solution works. Thanks!

blasmat commented 8 years ago

This solution works for me as well, but I am finding that it reverts itself so that I need to modify the map line in .redshiftgrc each time I want to start redshift. Any permanent solution available?

ghost commented 8 years ago

The file is indeed sometimes overwritten by redshift; i assume this line: options.c 318 must be changed to while( (currstr=strchr(currstr,, ',') || currstr=strchr(currstr, '|')) ){as a workaround. Or line options.c 449 to fprintf(fid_config,"%.2f,%.2f;",Rs_opts.map[i].elev,Rs_opts.map[i].temp);

Since i don't have time to test and make a PR myself i will leave it to some one else.

edit: i also don't know the status of this project, it seems like it's not being updated any more

joksik commented 7 years ago

sorry for refresh but i have the same error. solution works but maybe somebody will fix this?

xorinet commented 3 years ago

One simple solution would be to go to /usr/bin/redshiftgui, and add this line after #!/bin/sh: find ~/.redshiftgrc -type f -exec sed -i 's/|/,/g' {} \; This might not be a perfect solution, but at least it works :stuck_out_tongue:

(sorry for saying this 3 or so years late)

dag7dev commented 2 years ago

@Xorinet no need to be sorry: I am here to write that as of 2022, this issue is still present.