Unable to load config file - permission denied #672

cbcoutinho · 2018-09-30T14:51:55Z

Describe the bug
Redshift (v1.12) is unable to read my config file

I have checked the FAQ and my issue is not mention there.

To Reproduce
install redshift on OpenSUSE Tumbleweed:

$ sudo zypper install redshift

Run redshift

$ redshift -c ~/.config/redshift/redshift.conf
fopen: Permission denied
Unable to load config file.

Not really sure what it means with 'permission denied':

$ ls -l ~/.config/redshift/redshift.conf
-rw-r--r-- 1 chris users chris 2.0K 2018-09-30 16:23 /home/chris/.config/redshift/redshift.conf

Without stating config file redshift tries to use geoclue2, which i don't want:

Trying location provider `geoclue2'...
Using provider `geoclue2'.
Solar elevations: day above 3.0, night below -6.0
Temperatures: 6500K at day, 4500K at night
Brightness: 1.00:1.00
Gamma (Daytime): 1.000, 1.000, 1.000
Gamma (Night): 1.000, 1.000, 1.000
Using method `randr'.
Waiting for initial location to become available...
Unable to start GeoClue client: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Geolocation disabled for UID 1000.
Access to the current location was denied by GeoClue!
Make sure that location services are enabled and that Redshift is permitted
to use location services. See https://github.com/jonls/redshift#faq for more
information.
Unable to get location from provider.

Expected behavior
Redshift reads my config file

Software versions (please complete the following information):

OS: OpenSUSE Tumbleweed running X
Redshift version: 1.12
Redshift installed from: OpenSUSE package manager (zypper)

My config. Note, it uses manual:
; Global settings for redshift
[redshift]
; Set the day and night screen temperatures
temp-day=5700
temp-night=3000

; Enable/Disable a smooth transition between day and night
; 0 will cause a direct change from day to night screen temperature.
; 1 will gradually increase or decrease the screen temperature.
transition=1

; Set the screen brightness. Default is 1.0.
;brightness=0.9
; It is also possible to use different settings for day and night
; since version 1.8.
;brightness-day=0.7
;brightness-night=0.4
; Set the screen gamma (for all colors, or each color channel
; individually)
gamma=0.8
;gamma=0.8:0.7:0.8
; This can also be set individually for day and night since
; version 1.10.
;gamma-day=0.8:0.7:0.8
;gamma-night=0.6

; Set the location-provider: 'geoclue', 'geoclue2', 'manual'
; type 'redshift -l list' to see possible values.
; The location provider settings are in a different section.

; Use manual if internet is out
;location-provider=geoclue2
location-provider=manual

; Set the adjustment-method: 'randr', 'vidmode'
; type 'redshift -m list' to see all possible values.
; 'randr' is the preferred method, 'vidmode' is an older API.
; but works in some cases when 'randr' does not.
; The adjustment method settings are in a different section.
adjustment-method=randr

; Configuration of the location-provider:
; type 'redshift -l PROVIDER:help' to see the settings.
; ex: 'redshift -l manual:help'
; Keep in mind that longitudes west of Greenwich (e.g. the Americas)
; are negative numbers.

; NOTE: These are not used if location-provider = geoclue2
; Amsterdam
[manual]
lat=52.3
lon=4.9

; Configuration of the adjustment-method
; type 'redshift -m METHOD:help' to see the settings.
; ex: 'redshift -m randr:help'
; In this example, randr is configured to adjust screen 1.
; Note that the numbering starts from 0, so this is actually the
; second screen. If this option is not specified, Redshift will try
; to adjust all screens.
;[randr]
;screen=1

The text was updated successfully, but these errors were encountered:

jonls · 2018-10-13T16:26:34Z

Thanks for the issue report. This seems most likely to be an issue with permissions somewhere in you config path. Maybe one of the directories in the path has the wrong permission? Have you checked the permissions of ~/.config, ~/.config/redshift, etc.? These need the execute (x) bit set. Check that the owner of these directories/file is also the same as the user that you're using to run Redshift.

Since this is unlikely to be a Redshift issue I'm closing this. Please feel free to reopen if you tried everything and still experience this issue.

cbcoutinho · 2018-10-13T23:29:49Z

Unfortunately, granting executable permissions to the redshift.conf file doesn't help with running redshift with a config file. I'm still getting `fopen: permission denied` errors. Are there anymore debug capabilities when running redshift besides verbose (-v)?

…

On Oct-13-18, Jon Lund Steffensen wrote: Thanks for the issue report. This seems most likely to be an issue with permissions somewhere in you config path. Maybe one of the directories in the path has the wrong permission? Have you checked the permissions of `~/.config`, `~/.config/redshift`, etc.? These need the execute (`x`) bit set. Check that the owner of these directories/file is also the same as the user that you're using to run Redshift. Since this is unlikely to be a Redshift issue I'm closing this. Please feel free to reopen if you tried everything and still experience this issue. -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #672 (comment)

jonls · 2018-10-15T16:21:46Z

Please reread my suggestion. You need x on the directories possibly.

cbcoutinho · 2018-10-15T16:45:30Z

All directories on my system have the `x` permissions (for all groups) by default. Also, I noticed after building `redshift` from source that the problem goes away - it seems that this issue is specific to the currently installed version of `redshift` on openSUSE Tumbleweed, which is built using the instructions here: https://build.opensuse.org/package/show/openSUSE:Factory/redshift I'm going to take it up with them, this doesn't seem to be a bug related to `redshift` itself but rather with how it's installed on openSUSE. Sorry for the trouble.

…

On Oct-15-18, Jon Lund Steffensen wrote: Please reread my suggestion. You need `x` on the *directories* possibly. -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #672 (comment)

jonls · 2018-10-15T17:17:31Z

Awesome, thanks!

cbcoutinho · 2018-10-18T14:18:07Z

This ended up being an issue with (open)SUSE's AppArmour, which didn't update the allowed config path from ~/.conf/redshift.conf to ~/.config/redshift/redshift.conf whenever that was changed as the default in redshift.

Related bug is https://bugzilla.suse.com/show_bug.cgi?id=1111906

davralin · 2021-06-27T09:39:54Z

In case someone else stumbles upon this message on other distro's, the relevant bug in debian is here

Related bugs: * https://bugzilla.suse.com/show_bug.cgi?id=1111906 * https://bugs.debian.org/988068 * jonls#672 * jonls#860 src/config-ini.c still looks for $HOME/.config/redshift.conf which fails to open because the apparmor profile doesn’t allow it. src/config-ini.c also does this: struct passwd *pwd = getpwuid(getuid()); char *home = pwd->pw_dir; Since getpwuid doesn’t have access to /etc/passwd* it returns NULL, causing a segmentation fault in the line thereafter. This code is not triggered if a config is specified (e.g. -c redshift.conf) or $HOME/.config/redshift.conf exists.

See jonls/redshift#672 .

Jalle19 · 2024-07-30T18:15:41Z

Four years later and this still doesn't work without users manually editing /etc/apparmor.d/usr.bin.redshift or placing the configuration in a location very much not specified in the README. Unbelievable.

I wouldn't even have had to deal with any of this if it wasn't for geoclue2 shitting itself when Mozilla Location Services was axed some time ago, and the community as usual has literally no idea how to deal with it.

Booligoosh · 2024-09-20T10:53:25Z

Moving the file from ~/.config/redshift/redshift.conf to ~/.config/redshift.conf fixed it for me (Debian-based distro)

jonls self-assigned this Oct 1, 2018

jonls closed this as completed Oct 13, 2018

jonls added the question label Oct 13, 2018

yannickperrenet mentioned this issue Nov 6, 2021

Hooks not running #850

Closed

1 task

yannickperrenet mentioned this issue Dec 27, 2021

wrong path for .conf in README #845

Open

1 task

rumpeltux mentioned this issue Apr 18, 2022

Fix apparmor config. #864

Open

ntc2 added a commit to ntc2/conf that referenced this issue Apr 8, 2023

[redshift] Install redshift conf as hardlink because apparmor :/

a5e92d8

See jonls/redshift#672 .

wiltwong mentioned this issue Dec 22, 2023

running redshift on dedian returns a “Segmentation fault” #793

Open

1 task

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Unable to load config file - permission denied #672

Unable to load config file - permission denied #672

cbcoutinho commented Sep 30, 2018

jonls commented Oct 13, 2018

cbcoutinho commented Oct 13, 2018 via email

jonls commented Oct 15, 2018

cbcoutinho commented Oct 15, 2018 via email

jonls commented Oct 15, 2018

cbcoutinho commented Oct 18, 2018

davralin commented Jun 27, 2021

Jalle19 commented Jul 30, 2024

Booligoosh commented Sep 20, 2024

Unable to load config file - permission denied #672

Unable to load config file - permission denied #672

Comments

cbcoutinho commented Sep 30, 2018

jonls commented Oct 13, 2018

cbcoutinho commented Oct 13, 2018 via email

jonls commented Oct 15, 2018

cbcoutinho commented Oct 15, 2018 via email

jonls commented Oct 15, 2018

cbcoutinho commented Oct 18, 2018

davralin commented Jun 27, 2021

Jalle19 commented Jul 30, 2024

Booligoosh commented Sep 20, 2024